nncp-freq \
nncp-log \
nncp-mincfg \
- nncp-newnode \
+ nncp-newcfg \
nncp-pkt \
nncp-stat \
nncp-toss \
nncp-mincfg:
GOPATH=$(GOPATH) go build -ldflags "$(LDFLAGS)" cypherpunks.ru/nncp/cmd/nncp-mincfg
-nncp-newnode:
- GOPATH=$(GOPATH) go build -ldflags "$(LDFLAGS)" cypherpunks.ru/nncp/cmd/nncp-newnode
+nncp-newcfg:
+ GOPATH=$(GOPATH) go build -ldflags "$(LDFLAGS)" cypherpunks.ru/nncp/cmd/nncp-newcfg
nncp-pkt:
GOPATH=$(GOPATH) go build -ldflags "$(LDFLAGS)" cypherpunks.ru/nncp/cmd/nncp-pkt
useful mainly for usage with @ref{nncp-xfer} that has to know only
neighbours, without private keys involving.
-@node nncp-newnode
-@section nncp-newnode
+@node nncp-newcfg
+@section nncp-newcfg
@verbatim
-% nncp-newnode [options] > mynewnode.yaml
+% nncp-newcfg [options] > new.yaml
@end verbatim
-Generate new node: private keys, example configuration file and print it
-to stdout. You must use this command when you setup the new node.
+Generate new node configuration: private keys, example configuration
+file and print it to stdout. You must use this command when you setup
+the new node.
Pay attention that private keys generation consumes an entropy from your
operating system.
following workflow:
@enumerate
-@item Run @ref{nncp-newnode} on each node to create an initial
+@item Run @ref{nncp-newcfg} 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
along with this program. If not, see <http://www.gnu.org/licenses/>.
*/
-// Generate new NNCP node keys
+// Generate new NNCP node keys and configuration file
package main
import (
func usage() {
fmt.Fprintf(os.Stderr, nncp.UsageHeader())
- fmt.Fprintln(os.Stderr, "nncp-newnode -- generate new node keys\nOptions:")
+ fmt.Fprintln(os.Stderr, "nncp-newcfg -- generate new configuration and keys\nOptions:")
flag.PrintDefaults()
}