Change Go's website address

[nncp.git] / doc / workflow.texi

diff --git a/doc/workflow.texi b/doc/workflow.texi
index 7803a78d72d1235bbcba87d23faedae03dd112f6..8015b163e48b23cdb0b19a136b569452819fbe32 100644 (file)
--- a/doc/workflow.texi
+++ b/doc/workflow.texi
@@ -5,17 +5,17 @@ NNCP consists of several utilities. As a rule you will have the
 following workflow:
 
 @enumerate
-@item Run @ref{nncp-newnode} on each node to create an initial
+@item Run @ref{nncp-cfgnew} on each node to create an initial
 @ref{Configuration, configuration} file.
 @item Tune it up and set at least @ref{Spool, spool} and log paths.
 @item Share your public keys and reachability addressees with your
 neighbours. Add their keys to your configuration file and do any other
 required configuration about their reachability, permissions of file or
 freq transmission.
-@item Use @ref{nncp-file}, @ref{nncp-freq}, @ref{nncp-mail}
-(@ref{Postfix, look how} Postfix SMTP server could be configured)
-commands to queue file, freq and mail transmissions. Repeat as
-many times any time as you wish.
+@item Use @ref{nncp-file}, @ref{nncp-freq}, @ref{nncp-exec}
+(look @ref{Postfix, how} Postfix and @ref{Exim, how} Exim SMTP servers
+could be configured) commands to queue file, freq and exec
+transmissions. Repeat as many times any time as you wish.
 @item Depending on connection methods, either:
     @itemize
     @item run @ref{nncp-daemon} to accept remotely initiated connections
@@ -24,9 +24,21 @@ many times any time as you wish.
     connection to required nodes from time to time
     @item use @ref{nncp-xfer} with removable storage devices for copying
     packets to/from other nodes
+    @item use @ref{nncp-bundle} with either sequential storage devices
+    or broadcasting transmissions for copying packets
     @end itemize
 @item After successful packet exchanging (or just simply from time to
 time), run @ref{nncp-toss} for tossing (decrypting and processing) all
-inbound queues to receive mail messages, files, file requests and relay
+inbound queues to receive exec messages, files, file requests and relay
 transition packets to other nodes.
 @end enumerate
+
+@itemize
+@item If you wish to encrypt your configuration file containing your
+private keys, then use @ref{nncp-cfgenc} utility. You can always use an
+encrypted config without decrypting it in temporary memory file.
+@item If you wish to strip off any private keys from your config, then
+use @ref{nncp-cfgmin} utility. It will be useful for transferring
+messages with offline methods, but tossing them later on the machine
+with private keys.
+@end itemize