4 Nearly all commands have the following common options:
8 Path to configuration file. May be overridden by @env{NNCPCFG}
9 environment variable. If file file is an encrypted @ref{EBlob,
10 eblob}, then ask for passphrase to decrypt it first.
12 Print debug messages. Normally this option should not be used.
15 Minimal required resulting packet size, in KiBs. For example if you
16 send 2 KiB file and set @option{-minsize 4}, then resulting packet
17 will be 4 KiB (containing file itself and some junk).
19 Set desired outgoing packet @ref{Niceness, niceness level}.
21 Set desired reply packet @ref{Niceness, niceness level}. Only freq
22 and exec packets look at that niceness level.
24 Override @ref{CfgVia, via} configuration option for destination node.
25 Specified nodes must be separated with comma: @verb{|NODE1,NODE2|}.
26 With @verb{|-via -|} you can disable relaying at all.
28 Override path to spool directory. May be specified by
29 @env{NNCPSPOOL} environment variable.
31 Override path to logfile. May be specified by @env{NNCPLOG}
34 Print only errors, omit simple informational messages. In any case
35 those messages are logged, so you can reread them using
36 @ref{nncp-log} command.
37 @item -progress, -noprogress
38 Either force progress showing, or disable it.
40 Print version information.
42 Print warranty information (no warranty).
49 $ nncp-bundle [options] -tx [-delete] NODE [NODE ...] > ...
50 $ nncp-bundle [options] -rx -delete [-dryrun] [NODE ...] < ...
51 $ nncp-bundle [options] -rx [-check] [-dryrun] [NODE ...] < ...
54 With @option{-tx} option, this command creates @ref{Bundles, bundle} of
55 @ref{Encrypted, encrypted packets} from the spool directory and writes
58 With @option{-rx} option, this command takes bundle from stdin and
59 copies all found packets for our node to the spool directory. Pay
60 attention that @strong{no} integrity checking is done by default. Modern
61 tape drives could easily provide too much throughput your CPU won't be
62 able to verify on the fly. So if you won't @ref{nncp-toss, toss}
63 received packets at the place, it is advisable either to run
64 @ref{nncp-check} utility for packets integrity verification, or to use
65 @option{-check} option to enable on the fly integrity check.
67 You can specify multiple @option{NODE} arguments, telling for what nodes
68 you want to create the stream, or take it from. If no nodes are
69 specified for @option{-rx} mode, then all packets aimed at us will be
72 When packets are sent through the stream, they are still kept in the
73 spool directory, because there is no assurance that they are transferred
74 to the media (media (CD-ROM, tape drive, raw hard drive) can end). If
75 you want to forcefully delete them (after they are successfully flushed
76 to stdout) anyway, use @option{-delete} option.
78 But you can verify produced stream after, by digesting it by yourself
79 with @option{-rx} and @option{-delete} options -- in that mode, stream
80 packets integrity will be checked and they will be deleted from the
81 spool if everything is good. So it is advisable to recheck your streams:
84 $ nncp-bundle -tx ALICE BOB WHATEVER | cdrecord -tao -
85 $ dd if=/dev/cd0 bs=2048 | nncp-bundle -rx -delete
88 @option{-dryrun} option prevents any writes to the spool. This is
89 useful when you need to see what packets will pass by and possibly check
104 NODE[:ADDR] [FORCEADDR]
107 Call (connect to) specified @option{NODE} and run @ref{Sync,
108 synchronization} protocol with the @ref{nncp-daemon, daemon} on the
109 remote side. Normally this command could be run any time you wish to
110 either check for incoming packets, or to send out queued ones.
111 Synchronization protocol allows resuming and bidirectional packets
114 If @option{-rx} option is specified then only inbound packets
115 transmission is performed. If @option{-tx} option is specified, then
116 only outbound transmission is performed. @option{-onlinedeadline}
117 overrides @ref{CfgOnlineDeadline, @emph{onlinedeadline}}.
118 @option{-maxonlinetime} overrides @ref{CfgMaxOnlineTime,
119 @emph{maxonlinetime}}. @option{-rxrate}/@option{-txrate} override
120 @ref{CfgXxRate, rxrate/txrate}. @option{-list} option allows you to list
121 packets of remote node, without any transmission.
123 You can specify what packets your want to download, by specifying
124 @option{-pkts} option with comma-separated list of packets identifiers.
126 Each @option{NODE} can contain several uniquely identified
127 @option{ADDR}esses in @ref{CfgAddrs, configuration} file. If you do
128 not specify the exact one, then all will be tried until the first
129 success. Optionally you can force @option{FORCEADDR} address usage,
130 instead of addresses taken from configuration file. You can specify both
131 @verb{|host:port|} and @verb{#|some command#} formats.
133 Pay attention that this command runs integrity check for each completely
134 received packet in the background. This can be time consuming.
135 Connection could be lost during that check and remote node won't be
136 notified that file is done. But after successful integrity check that
137 file is renamed from @file{.part} one and when you rerun
138 @command{nncp-call} again, remote node will receive completion
145 $ nncp-caller [options] [NODE ...]
148 Croned daemon that calls remote nodes from time to time, according to
149 their @ref{CfgCalls, @emph{calls}} configuration field.
151 Optional number of @option{NODE}s tells to ignore other ones.
152 Otherwise all nodes with specified @emph{calls} configuration
153 field will be called.
155 Look @ref{nncp-call} for more information.
161 $ nncp-cfgmin [options] [-s INT] [-t INT] [-p INT] cfg.hjson > cfg.hjson.eblob
162 $ nncp-cfgmin [options] -d cfg.hjson.eblob > cfg.hjson
165 This command allows you to encrypt provided @file{cfg.hjson} file with
166 the passphrase, producing @ref{EBlob, eblob}, to safely keep your
167 configuration file with private keys. This utility was written for users
168 who do not want (or can not) to use either @url{https://gnupg.org/,
169 GnuPG} or similar tools. That @file{eblob} file can be used directly in
170 @option{-cfg} option of nearly all commands.
172 @option{-s}, @option{-t}, @option{-p} are used to tune @file{eblob}'s
173 password strengthening function. Space memory cost (@option{-s}),
174 specified in number of BLAKE2b-256 blocks (32 bytes), tells how many
175 memory must be used for hashing -- bigger values are better, but slower.
176 Time cost (@option{-t}) tells how many rounds/iterations must be
177 performed -- bigger is better, but slower. Number of parallel jobs
178 (@option{-p}) tells how many computation processes will be run: this is
179 the same as running that number of independent hashers and then joining
180 their result together.
182 When invoked for encryption, passphrase is entered manually twice. When
183 invoked for decryption (@option{-d} option), it is asked once and exits
184 if passphrase can not decrypt @file{eblob}.
186 @option{-dump} options parses @file{eblob} and prints parameters used
187 during its creation. For example:
189 $ nncp-cfgenc -dump /usr/local/etc/nncp.hjson.eblob
190 Strengthening function: Balloon with BLAKE2b-256
191 Memory space cost: 1048576 bytes
193 Number of parallel jobs: 2
201 $ nncp-cfgmin [options] > stripped.hjson
204 Print out stripped configuration version: only path to @ref{Spool,
205 spool}, path to log file, neighbours public keys are stayed. This is
206 useful mainly for usage with @ref{nncp-xfer} that has to know only
207 neighbours, without private keys involving.
213 $ nncp-cfgnew [options] [-nocomments] > new.hjson
216 Generate new node configuration: private keys, example configuration
217 file and print it to stdout. You must use this command when you setup
218 the new node. @option{-nocomments} will create configuration file
219 without descriptive huge comments -- useful for advanced users.
221 Pay attention that private keys generation consumes an entropy from your
228 $ nncp-check [options]
231 Perform @ref{Spool, spool} directory integrity check. Read all files
232 that has Base32-encoded filenames and compare it with recalculated
233 BLAKE2b hash output of their contents. That supplementary command is
234 not used often in practice, if ever.
240 $ nncp-daemon [options] [-maxconn INT] [-bind ADDR] [-inetd]
243 Start listening TCP daemon, wait for incoming connections and run
244 @ref{Sync, synchronization protocol} with each of them. You can run
245 @ref{nncp-toss} utility in background to process inbound packets from
248 @option{-maxconn} option specifies how many simultaneous clients daemon
249 can handle. @option{-bind} option specifies @option{addr:port} it must
252 It could be run as @command{inetd} service, by specifying
253 @option{-inetd} option. Example inetd-entry:
256 uucp stream tcp6 nowait nncpuser /usr/local/bin/nncp-daemon nncp-daemon -inetd
263 $ nncp-exec [options] NODE HANDLE [ARG0 ARG1 ...]
266 Send execution command to @option{NODE} for specified @option{HANDLE}.
267 Body is read from stdin and compressed. After receiving, remote side
268 will execute specified @ref{CfgExec, handle} command with @option{ARG*}
269 appended and decompressed body fed to command's stdin.
271 For example, if remote side has following configuration file for your
276 sendmail: [/usr/sbin/sendmail, "-t"]
277 appender: ["/bin/sh", "-c", "cat >> /append"]
281 then executing @verb{|echo My message | nncp-exec -replynice 123 REMOTE
282 sendmail root@localhost|} will lead to execution of:
287 NNCP_SENDER=OurNodeId \
289 /usr/sbin/sendmail -t root@@localhost
292 If @ref{CfgNotify, notification} is enabled on the remote side for exec
293 handles, then it will sent simple letter after successful command
294 execution with its output in message body.
300 $ nncp-file [options] [-chunked INT] SRC NODE:[DST]
303 Send @file{SRC} file to remote @option{NODE}. @file{DST} specifies
304 destination file name in remote's @ref{CfgIncoming, incoming}
305 directory. If this file already exists there, then counter will be
308 This command queues file in @ref{Spool, spool} directory immediately
309 (through the temporary file of course) -- so pay attention that sending
310 2 GiB file will create 2 GiB outbound encrypted packet.
312 If @file{SRC} equals to @file{-}, then create an encrypted temporary
313 file and copy everything taken from stdin to it and use for outbound
314 packet creation. Pay attention that if you want to send 1 GiB of data
315 taken from stdin, then you have to have more than 2 GiB of disk space
316 for that temporary file and resulting encrypted packet. You can control
317 where temporary file will be stored using @env{TMPDIR} environment
318 variable. Encryption is performed in AEAD mode with
319 @url{https://cr.yp.to/chacha.html, ChaCha20}-@url{https://en.wikipedia.org/wiki/Poly1305, Poly1305}
320 algorithms. Data is splitted on 128 KiB blocks. Each block is encrypted
321 with increasing nonce counter.
323 If @file{SRC} points to directory, then
324 @url{https://pubs.opengroup.org/onlinepubs/9699919799/utilities/pax.html#tag_20_92_13_01, pax archive}
325 will be created on the fly with directory contents and destination
326 filename @file{.tar} appended. It @strong{won't} contain any entities
327 metainformation, but modification time with the names. UID/GID are set
328 to zero. Directories have 777 permissions, files have 666, for being
329 friendly with @command{umask}. Also each entity will have comment like
330 @verb{|Autogenerated by NNCP version X.Y.Z built with goXXX|}.
332 If @option{-chunked} is specified, then source file will be split
333 @ref{Chunked, on chunks}. @option{INT} is the desired chunk size in
334 KiBs. This mode is more CPU hungry. Pay attention that chunk is saved in
335 spool directory immediately and it is not deleted if any error occurs.
336 @option{-minsize} option is applied per each chunk. Do not forget about
337 @ref{ChunkedZFS, possible} ZFS deduplication issues. Zero
338 @option{-chunked} disables chunked transmission.
340 If @ref{CfgNotify, notification} is enabled on the remote side for
341 file transmissions, then it will sent simple letter after successful
348 $ nncp-freq [options] NODE:SRC [DST]
351 Send file request to @option{NODE}, asking it to send its @file{SRC}
352 file from @ref{CfgFreq, freq.path} directory to our node under @file{DST}
353 filename in our @ref{CfgIncoming, incoming} one. If @file{DST} is not
354 specified, then last element of @file{SRC} will be used.
356 If @ref{CfgNotify, notification} is enabled on the remote side for
357 file request, then it will sent simple letter after successful file
367 Parse @ref{Log, log} file and print out its records in human-readable form.
373 $ nncp-pkt [options] < pkt
374 $ nncp-pkt [options] [-decompress] -dump < pkt > payload
375 $ nncp-pkt -overheads
378 Low level packet parser. Normally it should not be used, but can help in
381 By default it will print packet's type, for example:
383 Packet type: encrypted
385 Sender: 2WHBV3TPZHDOZGUJEH563ZEK7M33J4UESRFO4PDKWD5KZNPROABQ
388 If you specify @option{-dump} option and provide an @ref{Encrypted,
389 encrypted} packet, then it will verify and decrypt it to stdout.
390 Encrypted packets contain @ref{Plain, plain} ones, that also can be fed
391 to @command{nncp-pkt}:
395 Payload type: transitional
396 Path: VHMTRWDOXPLK7BR55ICZ5N32ZJUMRKZEMFNGGCEAXV66GG43PEBQ
400 Path: stargrave@@stargrave.org
403 And with the @option{-dump} option it will give you the actual payload
404 (the whole file, mail message, and so on). @option{-decompress} option
405 tries to zstd-decompress the data from plain packet (useful for mail
408 @option{-overheads} options print encrypted, plain and size header overheads.
414 $ nncp-reass [options] [-dryrun] [-keep] [-dump] [-stdout] FILE.nncp.meta
415 $ nncp-reass [options] [-dryrun] [-keep] @{-all | -node NODE@}
418 Reassemble @ref{Chunked, chunked file} after @ref{nncp-toss, tossing}.
420 When called with @option{FILE} option, this command will reassemble only
421 it. When called with @option{-node} option, this command will try to
422 reassemble all @file{.nncp.meta} files found in @option{NODE}'s
423 @ref{CfgIncoming, incoming} directory. When called with @option{-all}
424 option, then cycle through all known nodes to do the same.
426 Reassembling process does the following:
429 @item Parses @ref{Chunked, @file{.nncp.meta}} file.
430 @item Checks existence and size of every @file{.nncp.chunkXXX}.
431 @item Verifies integrity of every chunk.
432 @item Concatenates all chunks, simultaneously removing them from filesystem.
435 That process reads the whole data twice. Be sure to have free disk
436 space for at least one chunk. Decrypted chunk files as a rule are saved
437 in pseudo-random order, so removing them during reassembly process will
438 likely lead to filesystem fragmentation. Reassembly process on
439 filesystems with deduplication capability should be rather lightweight.
441 If @option{-dryrun} option is specified, then only existence and
442 integrity checking are performed.
444 If @option{-keep} option is specified, then no
445 @file{.nncp.meta}/@file{.nncp.chunkXXX} files are deleted during
448 @option{-stdout} option outputs reassembled file to stdout, instead of
449 saving to temporary file with renaming after. This could be useful for
450 reassembling on separate filesystem to lower fragmentation effect,
451 and/or separate storage device for higher performance.
453 @option{-dump} option prints meta-file contents in human-friendly form.
454 It is useful mainly for debugging purposes. For example:
456 Original filename: testfile
457 File size: 3.8 MiB (3987795 bytes)
458 Chunk size: 1.0 MiB (1048576 bytes)
461 0: eac60d819edf40b8ecdacd0b9a5a8c62de2d15eef3c8ca719eafa0be9b894017
462 1: 013a07e659f2e353d0e4339c3375c96c7fffaa2fa00875635f440bbc4631052a
463 2: f4f883975a663f2252328707a30e71b2678f933b2f3103db8475b03293e4316e
464 3: 0e9e229501bf0ca42d4aa07393d19406d40b179f3922a3986ef12b41019b45a3
467 Do not forget about @ref{ChunkedZFS, possible} ZFS deduplication issues.
473 $ nncp-rm [options] -tmp
474 $ nncp-rm [options] -lock
475 $ nncp-rm [options] -node NODE -part
476 $ nncp-rm [options] -node NODE -seen
477 $ nncp-rm [options] -node NODE [-rx] [-tx]
478 $ nncp-rm [options] -node NODE -pkt PKT
481 This command is aimed to delete various files from your spool directory:
484 @item If @option{-tmp} option is specified, then it will delete all
485 temporary files in @file{spool/tmp} directory. Files may stay in it when
486 commands like @ref{nncp-file} fail for some reason.
487 @item If @option{-lock} option is specified, then all @file{.lock} files
488 will be deleted in your spool directory.
489 @item If @option{-pkt} option is specified, then @file{PKT} packet (its
490 Base32 name) will be deleted. This is useful when you see some packet
491 failing to be processed.
492 @item When either @option{-rx} or @option{-tx} options are specified
493 (maybe both of them), then delete all packets from that given queues. If
494 @option{-part} is given, then delete only @file{.part}ly downloaded
495 ones. If @option{-seen} option is specified, then delete only
503 $ nncp-stat [options] [-node NODE]
506 Print current @ref{Spool, spool} statistics about unsent and unprocessed
507 packets. For each node (unless @option{-node} specified) and each
508 niceness level there will be printed how many packets (with the total
509 size) are in inbound (Rx) and outbound (Tx) queues.
515 $ nncp-toss [options]
526 Perform "tossing" operation on all inbound packets. This is the tool
527 that decrypts all packets and processes all payload packets in them:
528 copies files, sends mails, sends out file requests and relays transition
529 packets. It should be run after each online/offline exchange.
531 @option{-dryrun} option does not perform any writing and sending, just
532 tells what it will do.
534 @option{-cycle} option tells not to quit, but to repeat tossing every
535 @option{INT} seconds in an infinite loop. That can be useful when
536 running this command as a daemon.
538 @option{-seen} option creates empty @file{XXX.seen} file after
539 successful tossing of @file{XXX} packet. @ref{nncp-xfer},
540 @ref{nncp-bundle}, @ref{nncp-daemon} and @ref{nncp-call} commands skip
541 inbound packets that has been already seen, processed and tossed. This
542 is helpful to prevent duplicates.
544 @option{-nofile}, @option{-nofreq}, @option{-noexec}, @option{-notrns}
545 options allow to disable any kind of packet types processing.
551 $ nncp-xfer [options] [-node NODE] [-mkdir] [-keep] [-rx|-tx] DIR
554 Search for directory in @file{DIR} containing inbound packets for us and
555 move them to local @ref{Spool, spool} directory. Also search for known
556 neighbours directories and move locally queued outbound packets to them.
557 This command is used for offline packets transmission.
559 If @option{-mkdir} option is specified, then outbound neighbour(s)
560 directories will be created. This is useful for the first time usage,
561 when storage device does not have any directories tree.
563 If @option{-keep} option is specified, then keep copied files, do not
566 @option{-rx} option tells only to move inbound packets addressed to us.
567 @option{-tx} option tells exactly the opposite: move only outbound packets.
569 @ref{nncp-cfgmin} could be useful for creating stripped minimalistic
570 configuration file version without any private keys.
572 @file{DIR} directory has the following structure:
573 @file{RECIPIENT/SENDER/PACKET}, where @file{RECIPIENT} is Base32 encoded
574 destination node, @file{SENDER} is Base32 encoded sender node.
576 Also look for @ref{nncp-bundle}, especially if you deal with CD-ROM and