3 .\" Manual for the administration protocol
5 .\" (c) 2008 Straylight/Edgeware
8 .\"----- Licensing notice ---------------------------------------------------
10 .\" This file is part of Trivial IP Encryption (TrIPE).
12 .\" TrIPE is free software: you can redistribute it and/or modify it under
13 .\" the terms of the GNU General Public License as published by the Free
14 .\" Software Foundation; either version 3 of the License, or (at your
15 .\" option) any later version.
17 .\" TrIPE is distributed in the hope that it will be useful, but WITHOUT
18 .\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
19 .\" FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
22 .\" You should have received a copy of the GNU General Public License
23 .\" along with TrIPE. If not, see <https://www.gnu.org/licenses/>.
25 .\"--------------------------------------------------------------------------
26 .so ../common/defs.man \" @@@PRE@@@
28 .\"--------------------------------------------------------------------------
29 .TH tripe-admin 5tripe "18 February 2001" "Straylight/Edgeware" "TrIPE: Trivial IP Encryption"
31 .\"--------------------------------------------------------------------------
34 tripe-admin \- administrator commands for TrIPE
36 .\"--------------------------------------------------------------------------
39 This manual page describes the administration interface provided by the
45 program can be used either interactively or in scripts to communicate
46 with the server using this interface. Alternatively, simple custom
47 clients can be written in scripting languages such as Perl, Python or
48 Tcl, or more advanced clients such as GUI monitors can be written in C
49 with little difficulty.
51 Administration commands use a textual protocol. Each client command or
52 server response consists of a line of ASCII text terminated by a single
53 linefeed character. No command may be longer than 255 characters.
54 .SS "General structure"
55 Each command or response line consists of a sequence of
56 whitespace-separated tokens. The number and nature of whitespace
57 characters separating two tokens in a client command is not significant;
58 the server always uses a single space character. The first token in a
61 identifying the type of command or response contained. Keywords in
62 client commands are not case-sensitive; the server always uses uppercase
65 In order to allow tokens to contain internal whitespace, a quoting
66 mechanism is provided. Whitespace within matched pairs of quotes \(en
71 \(en is considered to be internal. Any character (other than newline)
72 may be escaped by preceding it with a backslash
74 in particular, this can be used to include quote characters. It is
75 impossible for a token to contain a newline character.
77 On output, the server will use double quotes when necessary.
79 For simple client command, the server responds with zero or more
81 lines, followed by either an
87 provides information requested in the command. An
89 response contains no further data. A
91 code is followed by a machine-readable explanation of why the command
94 Simple command processing is strictly synchronous: the server reads a
95 command, processes it, and responds, before reading the next command.
96 All commands can be run as simple commands. Long-running commands
101 block the client until they finish, but the rest of the server continues
103 .B "Background commands"
104 to find out how to issue long-running commands without blocking.
105 .SS "Asynchronous broadcasts"
106 There are three types of asynchronous broadcast messages which aren't
107 associated with any particular command. Clients can select which
108 broadcast messages they're interested in using the
114 message contains a machine-readable message warning of an error
115 encountered while processing a command, unexpected or unusual behaviour
116 by a peer, or a possible attack by an adversary. Under normal
117 conditions, the server shouldn't emit any warnings.
121 message contains a human-readable tracing message containing diagnostic
122 information. Trace messages are controlled using the
124 command-line option to the server, or the
126 administration command (see below). Support for tracing can be disabled
127 when the package is being configured, and may not be available in your
132 message is a machine-readable notification about some routine but
133 interesting event such as creation or destruction of peers.
134 .SS "Background commands"
139 take a long time to complete. To prevent these long-running commands
140 from tying up a server connection, they can be run in the background.
141 Not all commands can be run like this: the ones that can provide a
143 option, which must be supplied with a
146 A command may fail before it starts running in the background. In this
147 case, the server emits a
149 response, as usual. To indicate that a command has started running in
150 the background, the server emits a response of the form
151 .BI "BGDETACH " tag \fR,
154 is the value passed to the
156 option. From this point on, the server is ready to process more
157 commands and reply to them.
159 Responses to background commands are indicated by a line beginning with
165 followed by the command tag. These correspond to the
170 responses for simple commands:
172 indicates information from a background command which has not completed
177 indicates that a background command succeeded or failed, respectively.
179 A background command will never issue an
183 response: it will always detach and then issue any
188 .SS "Client-provided services"
189 .\"* 25 Service-related messages
190 An administration client can provide services to other clients.
191 Services are given names and versions. A client can attempt to
193 a particular service by issuing the
195 command. This may fail, for example, if some other client already
196 provides the same or later version of the service.
198 Other clients can issue
199 .I "service commands"
202 command; the service provider is expected to handle these commands and
205 There are three important asynchronous messages which will be sent to
208 .BI "SVCCANCEL " jobid
209 The named job has been cancelled, either because the issuing client has
210 disconnected or explicitly cancelled the job using the
214 .BI "SVCCLAIM " service " " version
215 Another client has claimed a later version of the named
217 The recipient is no longer the provider of this service.
219 .BI "SVCJOB " jobid " " service " " command " " args \fR...
220 Announces the arrival of a new job. The
222 is a simple token consisting of alphanumeric characters which
224 uses to identify this job.
226 The service provider can reply to the job using the commands
231 The first of these sends an
233 response and leaves the job active; the other two send an
237 response respectively, and mark the job as being complete.
241 is a potentially long-running command, it can be run in the background.
242 This detail is hidden from service providers:
244 will issue the corresponding
246 responses when appropriate.)
247 .SS "Network addresses"
248 A network address is a sequence of tokens. The first is a token
249 identifying the network address family. The length of an address and
250 the meanings of the subsequent tokens depend on the address family.
251 Address family tokens are not case-sensitive on input; on output, they
252 are always in upper-case.
254 The following address families are recognized.
256 .BI "ANY " address " \fR[" port \fR]
257 An address and port number for any supported address family. On output,
259 never uses this form. On input, the
261 is examined: if it is a numeric address for some recognized address
262 family, then it is interpreted as such; otherwise it is looked up using
263 the DNS (in the background). The background resolver's address-sorting
266 simply takes the first address in the returned list which is of a
267 supported address family. Symbolic port numbers are permitted; if
268 omitted, the default port 4070 is used.
270 .BI "INET " address " \fR[" port \fR]
271 An Internet socket, naming an IPv4 address and UDP port. On output, the
273 is always in numeric dotted-quad form, and the
275 is given as a plain decimal number. On input, DNS hostnames and
276 symbolic port names are permitted; if omitted, the default port 4070 is
279 .BI "INET6 " address " \fR[" port \fR]
280 An Internet socket, naming an IPv6 address and UDP port. On output, the
282 is always in numeric hex-and-colons form, and the
284 is given as a plain decimal number. On input, DNS hostnames and
285 symbolic port names may be permitted, depending on how
287 was compiled; if omitted, the default port 4070 is used.
289 If, on input, no recognized address family token is found, the following
290 tokens are assumed to represent an
292 address. Addresses output by the server always have an address family
293 token, and do not use
296 Name resolution never blocks the main server, but will block the
297 requesting client, unless the command is run in the background.
298 .SS "Key-value output"
303 produce output in the form of
305 pairs, one per token. Neither the
311 Commands which enable or disable kinds of output (e.g.,
315 work in similar ways. They take a single optional argument, which
316 consists of a string of letters selecting message types, optionally
321 to disable, the subsequently listed types.
323 If the argument is omitted, the available message types are displayed,
326 line, in a fixed-column format. Column zero contains the key letter for
327 selecting that message type; column one contains either a space or a
329 sign, if the message type is disabled or enabled respectively; and a
330 textual description of the message type begins at column 3 and continues
331 to the end of the line.
333 Lowercase key letters control individual message types. Uppercase key
334 letters control collections of message types.
336 .\"--------------------------------------------------------------------------
337 .SH "COMMAND REFERENCE"
340 The commands provided are:
342 .BI "ADD \fR[" options "\fR] " peer " " address "\fR..."
343 Adds a new peer. The peer is given the name
345 the peer's public key is assumed to be in the file
347 (or whatever alternative file was specified in the
349 option on the command line). The
351 is the network address (see above for the format) at which the peer can
352 be contacted. The following options are recognized.
356 .BI "\-background " tag
357 Run the command in the background, using the given
361 Don't send an immediate challenge to the peer; instead, wait until it
362 sends us something before responding.
365 The association with the peer is not intended to persist indefinitely.
366 If a peer marked as ephemeral is killed, or the
368 daemon is shut down, send a
370 packet to the peer so that it forgets about us; if a peer marked as
373 packet then it is killed (but in this case no further
375 packet is sent). Peers not marked as ephemeral exhibit neither of these
376 behaviours; each peer must have the other marked as ephemeral for the
377 association to be fully torn down if either end kills the other.
379 .BI "\-keepalive " time
380 Send a no-op packet if we've not sent a packet to the peer in the last
382 interval. This is useful for persuading port-translating firewalls to
383 believe that the `connection' is still active. The
385 is expressed as a nonnegative integer followed optionally by
391 for days, hours, minutes, or seconds respectively; if no suffix is
392 given, seconds are assumed.
397 to authenticate the peer. The default is to use the key tagged
400 .BI "\-knock \fR[" prefix .\fR] tag
402 .RI [ prefix\fB. ] tag
407 messages to the peer during key-exchange. The string as a whole should
408 name the local machine to the peer, and
410 should name its public key. When such messages are received from a
411 currently unknown peer,
415 notification stating the peer's (claimed) name and address. The server
416 will already have verified that the sender is using the peer's private
417 key by this point. This option implies
421 The peer is a mobile device, and is likely to change address rapidly.
422 If a packet arrives from an unknown address, the server's usual response
423 is to log a warning and discard it. If the server knows of any mobile
424 peers, however, it will attempt to decrypt the packet using their keys,
425 and if one succeeds, the server will update its idea of the peer's
428 notification. This option implies
434 to authenticate to the peer. The default is to use the key named in the
436 command-line option, or a key with type
444 .BI "\-tunnel " tunnel
445 Use the named tunnel driver, rather than the default.
452 line reporting the IP address and port number stored for
455 .BI "ALGS \fR[" peer \fR]
456 Emits information about the cryptographic algorithms in use, in
459 is given, then describe the algorithms used in the association with that
460 peer; otherwise describe the default algorithms.
463 The keys are as follows.
466 Type of key-exchange group in use, currently either
471 .B kx-group-order-bits
472 Length of the group order, in bits. This gives an approximate measure
473 of the group strength.
476 Length of a group element, in bits. This may be useful when analyzing
480 The hash function in use, e.g.,
484 The mask-generating function in use, e.g.,
488 The size of the hash function's output, in octets.
491 The name of the bulk-crypto transform.
494 The amount of overhead, in bytes, caused by the crypto transform.
497 The name of the bulk data cipher in use, e.g.,
501 The length of key used by the bulk data cipher, in octets.
504 The block size of the bulk data cipher, or zero if it's not based on a
508 The maximum amount of data to be encrypted using a single key. (A new
509 key exchange is instigated well before the limit is reached, in order to
510 allow for a seamless changeover of keys.)
513 The message authentication algorithm in use, e.g.,
517 The length of the key used by the message authentication algorithm, in
521 The length of the message authentication tag, in octets.
524 The block cipher in use, e.g.,
528 The length of key used by the block cipher, in octets.
531 The block size of the block cipher.
533 The various sizes are useful, for example, when computing the MTU for a
536 is the MTU of the path to the peer, then the tunnel MTU should be
546 = 20 (IPv4) or 40 (IPv6) bytes of IP header, 8 bytes of UDP header, a
547 packet type octet, and the bulk-crypto transform overhead (which
548 includes the sequence number).
552 Cancels the background job with the named
555 .BI "CHECKCHAL " challenge
556 Verifies a challenge as being one earlier issued by
558 and not previously either passed to
560 or in a greeting message.
563 Causes the server to disassociate itself from its terminal and become a
564 background task. This only works once. A notification is issued.
566 .BI "EPING \fR[" options "\fR] " peer
567 Sends an encrypted ping to the peer, and expects an encrypted response.
568 This checks that the peer is running (and not being impersonated), and
569 that it can encrypt and decrypt packets correctly. Options and
570 responses are the same as for the
575 Requests the server to begin a new key exchange with
580 Requests a challenge. The challenge is returned in an
582 line, as a base64-encoded string. See
585 .BI "GREET " peer " " challenge
586 Sends a greeting packet containing the
588 (base-64 encoded) to the named
590 The expectation is that this will cause the peer to recognize us and
591 begin a key-exchange.
594 Causes the server to emit an
596 line for each command it supports. Each line lists the command name,
597 followed by the names of the arguments. This may be helpful as a memory
598 aid for interactive use, or for program clients probing for features.
603 line containing the name of the network interface used to collect IP
604 packets which are to be encrypted and sent to
606 Used by configuration scripts so that they can set up routing tables
607 appropriately after adding new peers.
612 line giving the tag for each outstanding background job.
615 Causes the server to forget all about
617 All keys are destroyed, and no more packets are sent. No notification
618 is sent to the peer: if it's important that the peer be notified, you
619 must think of a way to do that yourself.
622 For each currently-known peer, an
624 line is written containing the peer's name, as given to
627 .BI "NOTIFY " tokens\fR...
630 notification to all interested administration clients.
633 Returns information about a peer, in key-value form. The following keys
638 The tunnel driver used for this peer.
641 The keepalive interval, in seconds, or zero if no keepalives are to be
645 If present, the string sent to the peer to set up the association; see
655 The (short) key tag being used for the peer, as passed to the
660 The full key tag of the peer's public key currently being used. This
661 may change during the life of the association.
664 The private key tag being used for the peer, as passed to the
668 command-line option. If neither of these was given explicitly, the
669 private key tag is shown as
671 since there is no fixed tag used under these circumstances.
673 .B current-private-key
674 The full key tag of the private key currently being used for this
675 association. This may change during the life of the association.
682 depending on whether or not (respectively) key-exchange is waiting for
683 the peer to initiate.
690 depending on whether or not (respectively) the peer is expected to
691 change its address unpredictably.
698 depending on whether the association with the peer is expected to be
699 temporary or persistent (respectively).
702 .BI "PING \fR[" options "\fR] " peer
703 Send a transport-level ping to the peer. The ping and its response are
704 not encrypted or authenticated. This command, possibly in conjunction
705 with tracing, is useful for ensuring that UDP packets are actually
706 flowing in both directions. See also the
712 line is printed describing the outcome:
715 .BI "ping-ok " millis
716 A response was received
718 after the ping was sent.
721 No response was received within the time allowed.
724 The peer was killed (probably by another admin connection) before a
725 response was received.
728 Options recognized for this command are:
732 .BI "\-background " tag
733 Run the command in the background, using the given
736 .BI "\-timeout " time
739 seconds before giving up on a response. The default is 5 seconds. The
741 is expressed as a nonnegative integer followed optionally by
747 for days, hours, minutes, or seconds respectively; if no suffix is
748 given, seconds are assumed.
756 line containing just the number of the UDP port used by the
758 server, for the given address
760 (or one chosen arbitrarily if omitted -- though
762 tries to use the same port number consistently so this is not a likely
763 problem in practice). If you've allowed your server to allocate a port
764 dynamically, this is how to find out which one it chose.
767 Instructs the server to recheck its keyring files. The server checks
768 these periodically anyway but it may be necessary to force a recheck,
769 for example after adding a new peer key.
772 Instructs the server to exit immediately. A warning is sent.
775 Returns information about the server, in the form of key-value pairs.
776 The following keys are used.
780 A keyword naming the implementation of the
782 server. The current implementation is called
786 The server's version number, as reported by
794 if the server has or hasn't (respectively) become a daemon.
797 .BI "SETIFNAME " peer " " new-name
798 Informs the server that the
800 tunnel-interface name has been changed to
802 This is useful if firewalling decisions are made based on interface
803 names: a setup script for a particular peer can change the name, and
804 then update the server's records so that they're accurate.
809 lines, each containing one or more statistics in the form
810 .IB name = value \fR.
811 The statistics-gathering is experimental and subject to change.
813 .BI "SVCCLAIM " service " " version
814 Attempts to claim the named
818 The claim is successful if the service is currently unclaimed, or if
819 a version earlier than
821 is provided; otherwise the command fails with the error
822 .BR "service-exists" .
824 .BI "SVCENSURE " service " \fR[" version \fR]
827 is provided, and (if specified) to at least the given
829 An error is reported if these conditions are not met; otherwise the
830 command succeeds silently.
832 .BI "SVCFAIL " jobid " " tokens \fR...
837 response to the service job with the given
841 as the reason for failure. The job is closed.
843 .BI "SVCINFO " jobid " " tokens \fR...
848 response to the service job with the given
852 as the info message. The job remains open.
855 Output a line of the form
862 for each service currently provided.
870 response to the service job with the given
874 .BI "SVCQUERY " service
877 lines in key-value format, describing the named
879 The following keys are used.
886 The service's version string.
889 .BI "SVCRELEASE " service
890 Announce that the client no longer wishes to provide the named
893 .BI "SVCSUBMIT \fR[" options "\fR] " service " " command " " arguments \fR...
894 Submit a job to the provider of the given
900 The following options are accepted.
904 .BI "\-background " tag
905 Run the command in the background, using the given
908 .BI "\-version " version
909 Ensure that at least the given
911 of the service is available before submitting the job.
915 .BR "TRACE " [\fIoptions\fP]
916 Selects trace outputs: see
918 above. Message types provided are:
921 Currently, the following tracing options are supported:
924 Tunnel events: reception of packets to be encrypted, and injection of
925 successfully-decrypted packets.
928 Peer management events: creation and destruction of peer attachments,
929 and arrival of messages.
932 Administration interface: acceptance of new connections, and handling of
933 the backgroud name-resolution required by the
938 Handling of symmetric keysets: creation and expiry of keysets, and
939 encryption and decryption of messages.
942 Key exchange: reception, parsing and emission of key exchange messages.
945 Key management: loading keys and checking for file modifications.
948 Display information about challenge issuing and verification.
951 Display contents of packets sent and received by the tunnel and/or peer
955 Display inputs, outputs and intermediate results of cryptographic
956 operations. This includes plaintext and key material. Use with
968 outputs provide extra detail for other outputs. Specifying
974 isn't useful; neither is specifying
985 For each available tunnel driver, an
987 line is printed giving its name.
990 Causes the server to emit an
992 line stating its software version, as two tokens: the server name, and
993 its version string. The server name
995 is reserved to the Straylight/Edgeware implementation.
997 .BR "WATCH " [\fIoptions\fP]
998 Enables or disables asynchronous broadcasts
999 .IR "for the current connection only" .
1002 above. The default watch state for the connection the server opens
1003 automatically on stdin/stdout is to show warnings and trace messages;
1004 other connections show no asynchronous broadcast messages. (This is
1005 done in order to guarantee that a program reading the server's stdout
1006 does not miss any warnings.)
1009 Message types provided are:
1027 .BI "WARN " tokens\fR...
1030 warning to all interested administration clients.
1032 .\"--------------------------------------------------------------------------
1033 .SH "ERROR MESSAGES"
1035 .\"* 20 Error messages (FAIL codes)
1040 messages are sent to clients as a result of errors during command
1043 .BI "already-daemon"
1048 server is already running as a daemon.
1050 .BI "bad-addr-syntax " message
1051 (For commands accepting socket addresses.) The address couldn't be
1054 .BI "bad-base64 " message
1055 (For commands accepting Base64-encoded input.) The Base64-encoded
1058 .BI "bad-syntax " cmd " " message
1059 (For any command.) The command couldn't be understood: e.g., the number
1060 of arguments was wrong.
1062 .BI "bad-time-spec " token
1065 is not a valid time interval specification. Acceptable time
1066 specifications are nonnegative integers followed optionally by
1072 for days, hours, minutes, or seconds, respectively.
1074 .BI "bad-trace-option " char
1077 An unknown trace option was requested.
1079 .BI "bad-watch-option " char
1082 An unknown watch option was requested.
1084 .BI "daemon-error " ecode " " message
1087 An error occurred during the attempt to become a daemon, as reported by
1090 .BI "disabled-address-family " afam
1097 is supported, but was disabled using command-line arguments.
1099 .BI "invalid-port " number
1102 The given port number is out of range.
1104 .BI "not-service-provider " service
1107 The invoking client is not the current provider of the named
1109 and is therefore not allowed to release it.
1111 .BI "peer-create-fail " peer
1116 failed for some reason. A warning should have been emitted explaining
1119 .BI "peer-addr-exists " address\fR...
1122 There is already a peer with the given
1125 .BI "peer-exists " peer
1128 There is already a peer named
1131 .B "ping-send-failed"
1132 The attempt to send a ping packet failed, probably due to lack of
1135 .B "provider-failed"
1138 The service provider disconnected without sending back a final reply to
1141 .B "provider-overloaded"
1144 The service provider has too many jobs queued up for it already.
1146 .BI "resolve-error " hostname
1151 could not be resolved.
1153 .BI "resolver-timeout " hostname
1158 took too long to resolve.
1160 .BI "service-exists " service " " version
1163 Another client is already providing the stated
1168 .BI "service-too-old " service " " version
1177 is available, which does not meet the stated requirements.
1179 .BI "tag-exists " tag
1180 (For long-running commands.) The named
1182 is already the tag of an outstanding job.
1184 .BI "unknown-address-family " afam
1191 .BI "unknown-command " token
1196 .BI "unknown-jobid " jobid
1204 is not recognized as identifying an outstanding job. It may have just
1207 .BI "unknown-peer " name
1215 There is no peer called
1218 .BI "unknown-port " port
1223 couldn't be found in
1226 .BI "unknown-service " service
1235 is not recognized as the name of a client-provided service.
1237 .BI "unknown-tag " tag
1242 is not the tag for any outstanding background job. It may have just
1245 .BI "unknown-tunnel " tun
1250 is not the name of any known tunnel driver.
1252 .\"--------------------------------------------------------------------------
1255 .\"* 30 Notification broadcasts (NOTE codes)
1256 The following notifications are sent to clients who request them.
1258 .BI "ADD " peer " " ifname " " address \fR...
1259 A new peer has been added. The peer's name is
1261 its tunnel is network interface
1263 and its network address is
1267 The server has forked off into the sunset and become a daemon.
1269 .BI "GREET " challenge " " address \fR...
1270 A valid greeting was received, with the given challenge (exactly as it
1280 .BI "KNOCK " peer " " address
1281 The currently unknown
1283 is attempting to connect from
1289 finished successfully.
1294 has begun or restarted. If key exchange keeps failing, this message
1295 will be repeated periodically.
1297 .BI "NEWADDR " peer " " address
1300 IP address has been changed to
1303 .BI "NEWIFNAME " peer " " old-name " " new-name
1306 tunnel interface name has been changed from
1314 .BI "SVCCLAIM " service " " version
1317 is now available, at the stated
1320 .BI "SVCRELEASE " service
1323 is no longer available.
1325 .BI "USER " tokens\fR...
1326 An administration client issued a notification using the
1330 .\"--------------------------------------------------------------------------
1333 .\"* 40 Warning broadcasts (WARN codes)
1335 There are many possible warnings. They are categorized according to
1338 Many of these warnings report system errors. These are reported as a
1339 pair of tokens, described below as
1345 is a string of the form
1349 value of the error; the
1351 is the `human-readable' form of the message, as reported by
1353 .SS "ABORT warnings"
1354 These all indicate that the
1356 server has become unable to continue. If enabled, the server will dump
1357 core in its configuration directory.
1359 .BI "ABORT repeated-select-errors"
1360 The main event loop is repeatedly failing. If the server doesn't quit,
1361 it will probably waste all available CPU doing nothing.
1362 .SS "ADMIN warnings"
1363 These indicate a problem with the administration socket interface.
1365 .BI "ADMIN accept-error " ecode " " message
1366 There was an error while attempting to accept a connection from a new
1369 .BI "ADMIN client-write-error " ecode " " message
1370 There was an error sending data to a client. The connection to the
1371 client has been closed.
1373 These indicate errors in challenges, either in the
1375 command or in greeting packets.
1377 .B "CHAL impossible-challenge"
1378 The server hasn't issued any challenges yet. Quite how anyone else
1379 thought he could make one up is hard to imagine.
1381 .B "CHAL incorrect-tag"
1382 Challenge received contained the wrong authentication data. It might be
1383 very stale, or a forgery.
1385 .B "CHAL invalid-challenge"
1386 Challenge received was the wrong length. We might have changed MAC
1387 algorithms since the challenge was issued, or it might just be rubbish.
1389 .B "CHAL replay duplicated-sequence"
1390 Challenge received was a definite replay of an old challenge. Someone's
1393 .B "CHAL replay old-sequence"
1394 Challenge received was old, but maybe not actually a replay. Try again.
1395 .SS "KEYMGMT warnings"
1396 These indicate a problem with the keyring files, or the keys stored in
1397 them. The first token is either
1403 in the descriptions below) indicating which keyring file is problematic,
1404 and the second token is the filename of the keyring. Frequently a key
1405 tag may be given next, preceded by the token
1408 .BI "KEYMGMT private-keyring " file " key " tag " incorrect-public-key"
1409 The private key doesn't record the correct corresponding public key.
1411 .BI "KEYMGMT public-keyring " file " key " tag " algorithm-mismatch"
1412 A peer's public key doesn't request the same algorithms as our private
1415 .BI "KEYMGMT " which "-keyring " file " key " tag " bad-tag-length " len
1416 The key attributes specify the length of MAC tag as
1418 but this is an invalid value \(en either too large or not a multiple of
1421 .BI "KEYMGMT " which "-keyring " file " key " tag " bad-tag-length-string " str
1422 The key attributes contain
1424 where a MAC tag length was expected. The key was generated wrongly.
1426 .BI "KEYMGMT private-keyring " file " key " tag " changed-group"
1427 The private keyring has been changed, but the new private key can't be
1428 used because it uses a different group for Diffie\(enHellman key
1431 .BI "KEYMGMT " which "-keyring " file " io-error " ecode " " message
1432 A system error occurred while opening or reading the keyring file.
1434 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-bulk-transform " bulk
1435 The key specifies the use of an unknown bulk-crypto transform
1437 Maybe the key was generated wrongly, or maybe the version of Catacomb
1438 installed is too old.
1440 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-cipher " cipher
1441 The key specifies the use of an unknown symmetric encryption algorithm
1443 Maybe the key was generated wrongly, or maybe the version of
1444 Catacomb installed is too old.
1446 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-group-type " type
1447 The key specifies the use of a Diffie\(enHellman group of an unknown
1449 Maybe the key was generated wrongly, or maybe the version of
1453 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-hash " hash
1454 The key specifies the use of an unknown hash function
1456 Maybe the key was generated wrongly, or maybe the version of Catacomb
1457 installed is too old.
1459 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-mac " mac
1460 The key specifies the use of an unknown message authentication code
1462 Maybe the key was generated wrongly, or maybe the version of Catacomb
1463 installed is too old.
1465 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-mgf-cipher " mgf
1466 The key specifies the use of an unknown symmetric encryption function
1468 for mask generation. Maybe the key was generated wrongly, or maybe the
1469 version of Catacomb installed is too old.
1471 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-serialization-format " ser
1472 The key specifies the use of an unknown serialization format
1474 for hashing group elements. Maybe the key was generated wrongly, or
1475 maybe the version of Catacomb installed is too old.
1477 .BI "KEYMGMT " which "-keyring " file " key " tag " no-hmac-for-hash " hash
1478 No message authentication code was given explicitly, and there's no
1479 implementation of HMAC for the selected hash function
1482 .BI "KEYMGMT " which "-keyring " file " key " tag " " alg " " name " no-key-size " hashsz
1489 The named algorithm requires more key material than the hash function
1490 can provide. You must change either the hash function, or the cipher or
1493 .BI "KEYMGMT " which "-keyring " file " key " tag " mgf " mgf " restrictive-key-schedule"
1494 The cipher selected for mask-generation is unsuitable because it can't
1495 accept arbitrary-sized keys.
1497 .BI "KEYMGMT " which "-keyring " file " key-not-found " tag
1500 couldn't be found in the keyring.
1502 .BI "KEYMGMT " which "-keyring " file " unknown-key-id 0x" keyid
1503 A key with the given
1505 (in hex) was requested but not found.
1507 .BI "KEYMGMT " which "-keyring " file " line " line " " message
1508 The contents of the keyring file are invalid. There may well be a bug
1513 These indicate problems during key-exchange. Many indicate either a bug
1514 in the server (either yours or the remote one), or some kind of attack
1515 in progress. All name a
1517 as the second token: this is the peer the packet is apparently from,
1518 though it may have been sent by an attacker instead.
1520 In the descriptions below,
1522 is one of the tokens
1534 .BI "KX " peer " algorithms-mismatch local-private-key " privtag " peer-public-key " pubtag
1535 The algorithms specified in the peer's public key
1537 don't match the ones described in the private key
1540 .BI "KX " peer " bad-expected-reply-log"
1543 uses in its protocol contain a check value which proves that the
1544 challenge is honest. This message indicates that the check value
1545 supplied is wrong: someone is attempting to use bogus challenges to
1548 server to leak private key information. No chance!
1550 .BI "KX " peer " decrypt-failed reply\fR|\fBswitch-ok"
1551 A symmetrically-encrypted portion of a key-exchange message failed to
1554 .BI "KX " peer " invalid " msgtoken
1555 A key-exchange message was malformed. This almost certainly indicates a
1558 .BI "KX " peer " incorrect cookie\fR|\fBswitch-rq\fR|\fBswitch-ok"
1559 A message didn't contain the right magic data. This may be a replay of
1560 some old exchange, or random packets being sent in an attempt to waste
1563 .BI "KX " peer " " which "-key-expired"
1564 The local private key or the peer's public key (distinguished by
1566 has expired. Either you or the peer's maintainer should have arranged
1567 for a replacement before now.
1569 .BI "KX " peer " sending-cookie"
1570 We've received too many bogus pre-challenge messages. Someone is trying
1571 to flood us with key-exchange messages and make us waste CPU on doing
1572 hard asymmetric crypto sums.
1574 .BI "KX " peer " unexpected " msgtoken
1575 The message received wasn't appropriate for this stage of the key
1576 exchange process. This may mean that one of our previous packets got
1579 it may simply mean that the peer has recently restarted.
1581 .BI "KX " peer " unknown-challenge"
1582 The peer is asking for an answer to a challenge which we don't know
1583 about. This may mean that we've been inundated with challenges from
1584 some malicious source
1585 .I who can read our messages
1586 and discarded the valid one.
1588 .BI "KX " peer " unknown-message 0x" nn
1589 An unknown key-exchange message arrived.
1591 These are largely concerned with management of peers and the low-level
1592 details of the network protocol. The second token is usually the name of
1595 if none is relevant.
1597 .BI "PEER " peer " bad-packet no-type"
1598 An empty packet arrived. This is very strange.
1600 .BI "PEER " peer " bad-packet unknown-category 0x" nn
1601 The message category
1603 (in hex) isn't understood. Probably a strange random packet from
1604 somewhere; could be an unlikely bug.
1606 .BI "PEER " peer " bad-packet unknown-type 0x" nn
1609 (in hex) isn't understood. Probably a strange random packet from
1610 somewhere; could be an unlikely bug.
1612 .BI "PEER " peer " corrupt-encrypted-ping"
1613 The peer sent a ping response which matches an outstanding ping, but its
1614 payload is wrong. There's definitely a bug somewhere.
1616 .BI "PEER " peer " corrupt-transport-ping"
1617 The peer (apparently) sent a ping response which matches an outstanding
1618 ping, but its payload is wrong. Either there's a bug, or the bad guys
1619 are playing tricks on you.
1621 .BI "PEER " peer " decrypt-failed"
1622 An encrypted IP packet failed to decrypt. It may have been mangled in
1623 transit, or may be a very old packet from an expired previous session
1624 key. There is usually a considerable overlap in the validity periods of
1625 successive session keys, so this shouldn't occur unless the key exchange
1626 takes ages or fails.
1628 .BI "PEER " peer " malformed-encrypted-ping"
1629 The peer sent a ping response which is hopelessly invalid. There's
1630 definitely a bug somewhere.
1632 .BI "PEER " peer " malformed-transport-ping"
1633 The peer (apparently) sent a ping response which is hopelessly invalid.
1634 Either there's a bug, or the bad guys are playing tricks on you.
1636 .BI "PEER " peer " packet-build-failed"
1637 There wasn't enough space in our buffer to put the packet we wanted to
1638 send. Shouldn't happen.
1640 .BI "PEER \- socket-read-error " ecode " " message
1641 An error occurred trying to read an incoming packet.
1643 .BI "PEER " peer " socket-write-error " ecode " " message
1644 An error occurred attempting to send a network packet. We lost that
1647 .BI "PEER " address\fR... " socket-write-error " ecode " " message
1648 An error occurred attempting to send a network packet. We lost that
1651 .BI "PEER " peer " unexpected-encrypted-ping 0x" id
1652 The peer sent an encrypted ping response whose id doesn't match any
1653 outstanding ping. Maybe it was delayed for longer than the server was
1654 willing to wait, or maybe the peer has gone mad.
1656 .BI "PEER \- unexpected-source " address\fR...
1657 A packet arrived from
1659 (a network address \(en see above), but no peer is known at that
1660 address. This may indicate a misconfiguration, or simply be a result of
1661 one end of a connection being set up before the other.
1663 .BI "PEER " peer " unexpected-transport-ping 0x" id
1664 The peer (apparently) sent a transport ping response whose id doesn't
1665 match any outstanding ping. Maybe it was delayed for longer than the
1666 server was willing to wait, or maybe the peer has gone mad; or maybe
1667 there are bad people trying to confuse you.
1668 .SS "PRIVSEP warnings"
1669 These indicate problems with the privilege-separation helper process.
1670 (The server tries to drop its privileges when it starts up, leaving a
1671 privileged helper process behind which will create and hand over tunnel
1672 descriptors on request, but hopefully not do anything else especially
1673 dangerous. Tunnel descriptors are not completely safe, but this is
1674 probably better than nothing.)
1676 .BI "PRIVSEP child-exited " rc
1677 The helper process exited normally with status
1679 Status 0 means that it thought the server didn't want it any more; 1
1680 means that it was invoked incorrectly; 127 means that some system call
1683 .BI "PRIVSEP child-killed " sig
1684 The helper process was killed by signal number
1687 .BI "PRIVSEP child-died " status
1688 The helper process died in some unexpected way;
1689 .I status is the raw status code returned by
1691 because the server didn't understand how to decode it.
1693 .BI "PRIVSEP helper-died"
1694 A tunnel driver requires a tunnel descriptor from the helper, but the
1695 helper isn't running so this won't work.
1697 .BI "PRIVSEP helper-read-error " ecode " " message
1698 The server failed to read a response from the helper process.
1700 .BI "PRIVSEP helper-short-read"
1701 The helper process didn't send back enough data, and has likely crashed.
1703 .BI "PRIVSEP helper-write-error " ecode " " message
1704 The server failed to send a message to the helper process.
1706 .BI "PRIVSEP no-fd-from-helper"
1707 The helper process sent back a positive response, but didn't include the
1708 requested tunnel descriptor.
1710 .BI "PRIVSEP unknown-response-code"
1711 The helper process sent back an incomprehensible reply. It's probably
1712 very confused and may crash.
1713 .SS "SERVER warnings"
1714 These indicate problems concerning the server process as a whole.
1716 .BI "SERVER ignore signal " name
1717 A signal arrived, but the server ignored it. Currently this happens for
1719 because that's a popular way of telling daemons to re-read their
1720 configuration files. Since
1722 re-reads its keyrings automatically and has no other configuration
1723 files, it's not relevant, but it seemed better to ignore the signal than
1726 .BI "SERVER quit signal " \fR[\fInn\fR|\fIname\fR]
1727 A signal arrived and
1731 .BI "SERVER quit admin-request"
1732 A client of the administration interface issued a
1736 .BI "SERVER quit foreground-eof"
1737 The server is running in foreground mode (the
1739 option), and encountered end-of-file on standard input.
1741 .BI "SERVER select-error " ecode " " message
1742 An error occurred in the server's main event loop. This is bad: if it
1743 happens too many times, the server will abort.
1745 .BI "SERVER waitpid-error " ecode " " message
1746 The server was informed that one of its child processes had exited, but
1747 couldn't retrieve the child's status.
1749 These are concerned with the symmetric encryption and decryption
1752 .BI "SYMM replay old-sequence"
1753 A packet was received with an old sequence number. It may just have
1754 been delayed or duplicated, or it may have been an attempt at a replay
1757 .BI "SYMM replay duplicated-sequence"
1758 A packet was received with a sequence number we've definitely seen
1759 before. It may be an accidental duplication because the 'net is like
1760 that, or a deliberate attempt at a replay.
1762 These concern the workings of the system-specific tunnel driver. The
1763 second token is the name of the tunnel interface in question, or
1767 .BI "TUN \- bsd no-tunnel-devices"
1768 The driver couldn't find an available tunnel device. Maybe if you
1771 files, it will work.
1773 .BI "TUN \- " tun-name " open-error " device " " ecode " " message
1774 An attempt to open the tunnel device file
1778 .BI "TUN \- linux config-error " ecode " " message
1779 Configuring the Linux TUN/TAP interface failed.
1781 .BI "TUN " ifname " " tun-name " read-error " ecode " " message
1782 Reading from the tunnel device failed.
1784 .BI "TUN " ifname " " tun-name " write-error " ecode " " message
1785 Writing from the tunnel device failed.
1787 .BI "TUN " ifname " slip bad-escape"
1788 The SLIP driver encountered a escaped byte it wasn't expecting to see.
1789 The erroneous packet will be ignored.
1791 .BI "TUN " ifname " slip eof"
1792 The SLIP driver encountered end-of-file on its input descriptor.
1793 Pending data is discarded, and no attempt is made to read any more data
1794 from that interface ever.
1796 .BI "TUN " ifname " slip escape-end"
1797 The SLIP driver encountered an escaped `end' marker. This probably
1798 means that someone's been sending it junk. The erroneous packet is
1799 discarded, and we hope that we've rediscovered synchronization.
1801 .BI "TUN \- slip fork-error " ecode " " message
1802 The SLIP driver encountered an error forking a child process while
1803 allocating a new dynamic interface.
1805 .BI "TUN \- slip no-slip-interfaces"
1806 The driver ran out of static SLIP interfaces. Either preallocate more,
1807 or use dynamic SLIP interface allocation.
1809 .BI "TUN " ifname " slip overflow"
1810 The SLIP driver gave up reading a packet because it got too large.
1812 .BI "TUN \- slip pipe-error " ecode " " message
1813 The SLIP driver encountered an error creating pipes while allocating a
1814 new dynamic interface.
1816 .BI "TUN \- slip read-ifname-failed " ecode " " message
1817 The SLIP driver encountered an error reading the name of a dynamically
1818 allocated interface. Maybe the allocation script is broken.
1820 .BI "TUN \- unet config-error " ecode " " message
1821 Configuring the Linux Unet interface failed. Unet is obsolete and
1822 shouldn't be used any more.
1824 .BI "TUN \- unet getinfo-error " ecode " " message
1825 Reading information about the Unet interface failed. Unet is obsolete
1826 and shouldn't be used any more.
1828 These are issued by administration clients using the
1832 .BI "USER " tokens\fR...
1833 An administration client issued a warning.
1836 .\"--------------------------------------------------------------------------
1839 .SS "Command responses"
1842 .BI "BGFAIL " tag " " tokens \fR...
1843 .BI "BGINFO " tag " " tokens \fR...
1845 .BI "FAIL " tokens \fR...
1846 .BI "INFO " tokens \fR...
1851 .\"--------------------------------------------------------------------------
1857 .IR "The Trivial IP Encryption Protocol" .
1859 .\"--------------------------------------------------------------------------
1862 Mark Wooding, <mdw@distorted.org.uk>
1864 .\"----- That's all, folks --------------------------------------------------
~mdw / tripe / blob