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 At present, only one address family is understood.
256 .BI "INET " address " \fR[" port \fR]
257 An Internet socket, naming an IPv4 address and UDP port. On output, the
258 address is always in numeric dotted-quad form, and the port is given as
259 a plain number. On input, DNS hostnames and symbolic port names are
260 permitted; if omitted, the default port 4070 is used. Name resolution
261 does not block the main server, but will block the requesting client,
262 unless the command is run in the background.
264 If, on input, no recognized address family token is found, the following
265 tokens are assumed to represent an
267 address. Addresses output by the server always have an address family
269 .SS "Key-value output"
274 produce output in the form of
276 pairs, one per token. Neither the
282 Commands which enable or disable kinds of output (e.g.,
286 work in similar ways. They take a single optional argument, which
287 consists of a string of letters selecting message types, optionally
292 to disable, the subsequently listed types.
294 If the argument is omitted, the available message types are displayed,
297 line, in a fixed-column format. Column zero contains the key letter for
298 selecting that message type; column one contains either a space or a
300 sign, if the message type is disabled or enabled respectively; and a
301 textual description of the message type begins at column 3 and continues
302 to the end of the line.
304 Lowercase key letters control individual message types. Uppercase key
305 letters control collections of message types.
307 .\"--------------------------------------------------------------------------
308 .SH "COMMAND REFERENCE"
311 The commands provided are:
313 .BI "ADD \fR[" options "\fR] " peer " " address "\fR..."
314 Adds a new peer. The peer is given the name
316 the peer's public key is assumed to be in the file
318 (or whatever alternative file was specified in the
320 option on the command line). The
322 is the network address (see above for the format) at which the peer can
323 be contacted. The following options are recognized.
327 .BI "\-background " tag
328 Run the command in the background, using the given
332 Don't send an immediate challenge to the peer; instead, wait until it
333 sends us something before responding.
335 .BI "\-keepalive " time
336 Send a no-op packet if we've not sent a packet to the peer in the last
338 interval. This is useful for persuading port-translating firewalls to
339 believe that the `connection' is still active. The
341 is expressed as a nonnegative integer followed optionally by
347 for days, hours, minutes, or seconds respectively; if no suffix is
348 given, seconds are assumed.
353 to authenticate the peer. The default is to use the key tagged
357 The peer is a mobile device, and is likely to change address rapidly.
358 If a packet arrives from an unknown address, the server's usual response
359 is to log a warning and discard it. If the server knows of any mobile
360 peers, however, it will attempt to decrypt the packet using their keys,
361 and if one succeeds, the server will update its idea of the peer's
369 to authenticate to the peer. The default is to use the key named in the
371 command-line option, or a key with type
379 .BI "\-tunnel " tunnel
380 Use the named tunnel driver, rather than the default.
387 line reporting the IP address and port number stored for
390 .BI "ALGS \fR[" peer \fR]
391 Emits information about the cryptographic algorithms in use, in
394 is given, then describe the algorithms used in the association with that
395 peer; otherwise describe the default algorithms.
398 The keys are as follows.
401 Type of key-exchange group in use, currently either
406 .B kx-group-order-bits
407 Length of the group order, in bits. This gives an approximate measure
408 of the group strength.
411 Length of a group element, in bits. This may be useful when analyzing
415 The hash function in use, e.g.,
419 The mask-generating function in use, e.g.,
423 The size of the hash function's output, in octets.
426 The name of the bulk-crypto transform.
429 The amount of overhead, in bytes, caused by the crypto transform.
432 The name of the bulk data cipher in use, e.g.,
436 The length of key used by the bulk data cipher, in octets.
439 The block size of the bulk data cipher, or zero if it's not based on a
443 The maximum amount of data to be encrypted using a single key. (A new
444 key exchange is instigated well before the limit is reached, in order to
445 allow for a seamless changeover of keys.)
448 The message authentication algorithm in use, e.g.,
452 The length of the key used by the message authentication algorithm, in
456 The length of the message authentication tag, in octets.
459 The block cipher in use, e.g.,
463 The length of key used by the block cipher, in octets.
466 The block size of the block cipher.
468 The various sizes are useful, for example, when computing the MTU for a
471 is the MTU of the path to the peer, then the tunnel MTU should be
477 allowing 20 bytes of IP header, 8 bytes of UDP header, a packet type
478 octet, and the bulk-crypto transform overhead (which includes the
483 Cancels the background job with the named
486 .BI "CHECKCHAL " challenge
487 Verifies a challenge as being one earlier issued by
489 and not previously either passed to
491 or in a greeting message.
494 Causes the server to disassociate itself from its terminal and become a
495 background task. This only works once. A notification is issued.
497 .BI "EPING \fR[" options "\fR] " peer
498 Sends an encrypted ping to the peer, and expects an encrypted response.
499 This checks that the peer is running (and not being impersonated), and
500 that it can encrypt and decrypt packets correctly. Options and
501 responses are the same as for the
506 Requests the server to begin a new key exchange with
511 Requests a challenge. The challenge is returned in an
513 line, as a base64-encoded string. See
516 .BI "GREET " peer " " challenge
517 Sends a greeting packet containing the
519 (base-64 encoded) to the named
521 The expectation is that this will cause the peer to recognize us and
522 begin a key-exchange.
525 Causes the server to emit an
527 line for each command it supports. Each line lists the command name,
528 followed by the names of the arguments. This may be helpful as a memory
529 aid for interactive use, or for program clients probing for features.
534 line containing the name of the network interface used to collect IP
535 packets which are to be encrypted and sent to
537 Used by configuration scripts so that they can set up routing tables
538 appropriately after adding new peers.
543 line giving the tag for each outstanding background job.
546 Causes the server to forget all about
548 All keys are destroyed, and no more packets are sent. No notification
549 is sent to the peer: if it's important that the peer be notified, you
550 must think of a way to do that yourself.
553 For each currently-known peer, an
555 line is written containing the peer's name, as given to
558 .BI "NOTIFY " tokens\fR...
561 notification to all interested administration clients.
564 Returns information about a peer, in key-value form. The following keys
569 The tunnel driver used for this peer.
572 The keepalive interval, in seconds, or zero if no keepalives are to be
576 The (short) key tag being used for the peer, as passed to the
581 The full key tag of the peer's public key currently being used. This
582 may change during the life of the association.
585 The private key tag being used for the peer, as passed to the
589 command-line option. If neither of these was given explicitly, the
590 private key tag is shown as
592 since there is no fixed tag used under these circumstances.
594 .B current-private-key
595 The full key tag of the private key currently being used for this
596 association. This may change during the life of the association.
599 .BI "PING \fR[" options "\fR] " peer
600 Send a transport-level ping to the peer. The ping and its response are
601 not encrypted or authenticated. This command, possibly in conjunction
602 with tracing, is useful for ensuring that UDP packets are actually
603 flowing in both directions. See also the
609 line is printed describing the outcome:
612 .BI "ping-ok " millis
613 A response was received
615 after the ping was sent.
618 No response was received within the time allowed.
621 The peer was killed (probably by another admin connection) before a
622 response was received.
625 Options recognized for this command are:
629 .BI "\-background " tag
630 Run the command in the background, using the given
633 .BI "\-timeout " time
636 seconds before giving up on a response. The default is 5 seconds. The
638 is expressed as a nonnegative integer followed optionally by
644 for days, hours, minutes, or seconds respectively; if no suffix is
645 given, seconds are assumed.
652 line containing just the number of the UDP port used by the
654 server. If you've allowed your server to allocate a port dynamically,
655 this is how to find out which one it chose.
658 Instructs the server to recheck its keyring files. The server checks
659 these periodically anyway but it may be necessary to force a recheck,
660 for example after adding a new peer key.
663 Instructs the server to exit immediately. A warning is sent.
666 Returns information about the server, in the form of key-value pairs.
667 The following keys are used.
671 A keyword naming the implementation of the
673 server. The current implementation is called
677 The server's version number, as reported by
685 if the server has or hasn't (respectively) become a daemon.
688 .BI "SETIFNAME " peer " " new-name
689 Informs the server that the
691 tunnel-interface name has been changed to
693 This is useful if firewalling decisions are made based on interface
694 names: a setup script for a particular peer can change the name, and
695 then update the server's records so that they're accurate.
697 .BI "SVCCLAIM " service " " version
698 Attempts to claim the named
702 The claim is successful if the service is currently unclaimed, or if
703 a version earlier than
705 is provided; otherwise the command fails with the error
706 .BR "service-exists" .
708 .BI "SVCENSURE " service " \fR[" version \fR]
711 is provided, and (if specified) to at least the given
713 An error is reported if these conditions are not met; otherwise the
714 command succeeds silently.
716 .BI "SVCFAIL " jobid " " tokens \fR...
721 response to the service job with the given
725 as the reason for failure. The job is closed.
727 .BI "SVCINFO " jobid " " tokens \fR...
732 response to the service job with the given
736 as the info message. The job remains open.
739 Output a line of the form
746 for each service currently provided.
754 response to the service job with the given
758 .BI "SVCQUERY " service
761 lines in key-value format, describing the named
763 The following keys are used.
770 The service's version string.
773 .BI "SVCRELEASE " service
774 Announce that the client no longer wishes to provide the named
777 .BI "SVCSUBMIT \fR[" options "\fR] " service " " command " " arguments \fR...
778 Submit a job to the provider of the given
784 The following options are accepted.
788 .BI "\-background " tag
789 Run the command in the background, using the given
792 .BI "\-version " version
793 Ensure that at least the given
795 of the service is available before submitting the job.
802 lines, each containing one or more statistics in the form
803 .IB name = value \fR.
804 The statistics-gathering is experimental and subject to change.
806 .BR "TRACE " [\fIoptions\fP]
807 Selects trace outputs: see
809 above. Message types provided are:
812 Currently, the following tracing options are supported:
815 Tunnel events: reception of packets to be encrypted, and injection of
816 successfully-decrypted packets.
819 Peer management events: creation and destruction of peer attachments,
820 and arrival of messages.
823 Administration interface: acceptance of new connections, and handling of
824 the backgroud name-resolution required by the
829 Handling of symmetric keysets: creation and expiry of keysets, and
830 encryption and decryption of messages.
833 Key exchange: reception, parsing and emission of key exchange messages.
836 Key management: loading keys and checking for file modifications.
839 Display information about challenge issuing and verification.
842 Display contents of packets sent and received by the tunnel and/or peer
846 Display inputs, outputs and intermediate results of cryptographic
847 operations. This includes plaintext and key material. Use with
859 outputs provide extra detail for other outputs. Specifying
865 isn't useful; neither is specifying
876 For each available tunnel driver, an
878 line is printed giving its name.
881 Causes the server to emit an
883 line stating its software version, as two tokens: the server name, and
884 its version string. The server name
886 is reserved to the Straylight/Edgeware implementation.
888 .BR "WATCH " [\fIoptions\fP]
889 Enables or disables asynchronous broadcasts
890 .IR "for the current connection only" .
893 above. The default watch state for the connection the server opens
894 automatically on stdin/stdout is to show warnings and trace messages;
895 other connections show no asynchronous broadcast messages. (This is
896 done in order to guarantee that a program reading the server's stdout
897 does not miss any warnings.)
900 Message types provided are:
918 .BI "WARN " tokens\fR...
921 warning to all interested administration clients.
923 .\"--------------------------------------------------------------------------
926 .\"* 20 Error messages (FAIL codes)
931 messages are sent to clients as a result of errors during command
939 server is already running as a daemon.
941 .BI "bad-addr-syntax " message
942 (For commands accepting socket addresses.) The address couldn't be
945 .BI "bad-base64 " message
946 (For commands accepting Base64-encoded input.) The Base64-encoded
949 .BI "bad-syntax " cmd " " message
950 (For any command.) The command couldn't be understood: e.g., the number
951 of arguments was wrong.
953 .BI "bad-time-spec " token
956 is not a valid time interval specification. Acceptable time
957 specifications are nonnegative integers followed optionally by
963 for days, hours, minutes, or seconds, respectively.
965 .BI "bad-trace-option " char
968 An unknown trace option was requested.
970 .BI "bad-watch-option " char
973 An unknown watch option was requested.
975 .BI "daemon-error " ecode " " message
978 An error occurred during the attempt to become a daemon, as reported by
981 .BI "invalid-port " number
984 The given port number is out of range.
986 .BI "not-service-provider " service
989 The invoking client is not the current provider of the named
991 and is therefore not allowed to release it.
993 .BI "peer-create-fail " peer
998 failed for some reason. A warning should have been emitted explaining
1001 .BI "peer-addr-exists " address\fR...
1004 There is already a peer with the given
1007 .BI "peer-exists " peer
1010 There is already a peer named
1013 .B "ping-send-failed"
1014 The attempt to send a ping packet failed, probably due to lack of
1017 .BI "resolve-error " hostname
1022 could not be resolved.
1024 .BI "resolver-timeout " hostname
1029 took too long to resolve.
1031 .BI "service-exists " service " " version
1034 Another client is already providing the stated
1039 .BI "service-too-old " service " " version
1048 is available, which does not meet the stated requirements.
1050 .BI "tag-exists " tag
1051 (For long-running commands.) The named
1053 is already the tag of an outstanding job.
1055 .BI "unknown-command " token
1060 .BI "unknown-jobid " jobid
1068 is not recognized as identifying an outstanding job. It may have just
1071 .BI "unknown-peer " name
1079 There is no peer called
1082 .BI "unknown-port " port
1087 couldn't be found in
1090 .BI "unknown-service " service
1099 is not recognized as the name of a client-provided service.
1101 .BI "unknown-tag " tag
1106 is not the tag for any outstanding background job. It may have just
1109 .\"--------------------------------------------------------------------------
1112 .\"* 30 Notification broadcasts (NOTE codes)
1113 The following notifications are sent to clients who request them.
1115 .BI "ADD " peer " " ifname " " address \fR...
1116 A new peer has been added. The peer's name is
1118 its tunnel is network interface
1120 and its network address is
1124 The server has forked off into the sunset and become a daemon.
1126 .BI "GREET " challenge " " address \fR...
1127 A valid greeting was received, with the given challenge (exactly as it
1140 finished successfully.
1145 has begun or restarted. If key exchange keeps failing, this message
1146 will be repeated periodically.
1148 .BI "NEWADDR " peer " " address
1151 IP address has been changed to
1154 .BI "NEWIFNAME " peer " " old-name " " new-name
1157 tunnel interface name has been changed from
1165 .BI "SVCCLAIM " service " " version
1168 is now available, at the stated
1171 .BI "SVCRELEASE " service
1174 is no longer available.
1176 .BI "USER " tokens\fR...
1177 An administration client issued a notification using the
1181 .\"--------------------------------------------------------------------------
1184 .\"* 40 Warning broadcasts (WARN codes)
1186 There are many possible warnings. They are categorized according to
1189 Many of these warnings report system errors. These are reported as a
1190 pair of tokens, described below as
1196 is a string of the form
1200 value of the error; the
1202 is the `human-readable' form of the message, as reported by
1204 .SS "ABORT warnings"
1205 These all indicate that the
1207 server has become unable to continue. If enabled, the server will dump
1208 core in its configuration directory.
1210 .BI "ABORT repeated-select-errors"
1211 The main event loop is repeatedly failing. If the server doesn't quit,
1212 it will probably waste all available CPU doing nothing.
1213 .SS "ADMIN warnings"
1214 These indicate a problem with the administration socket interface.
1216 .BI "ADMIN accept-error " ecode " " message
1217 There was an error while attempting to accept a connection from a new
1220 .BI "ADMIN client-write-error " ecode " " message
1221 There was an error sending data to a client. The connection to the
1222 client has been closed.
1224 These indicate errors in challenges, either in the
1226 command or in greeting packets.
1228 .B "CHAL impossible-challenge"
1229 The server hasn't issued any challenges yet. Quite how anyone else
1230 thought he could make one up is hard to imagine.
1232 .B "CHAL incorrect-tag"
1233 Challenge received contained the wrong authentication data. It might be
1234 very stale, or a forgery.
1236 .B "CHAL invalid-challenge"
1237 Challenge received was the wrong length. We might have changed MAC
1238 algorithms since the challenge was issued, or it might just be rubbish.
1240 .B "CHAL replay duplicated-sequence"
1241 Challenge received was a definite replay of an old challenge. Someone's
1244 .B "CHAL replay old-sequence"
1245 Challenge received was old, but maybe not actually a replay. Try again.
1246 .SS "KEYMGMT warnings"
1247 These indicate a problem with the keyring files, or the keys stored in
1248 them. The first token is either
1254 in the descriptions below) indicating which keyring file is problematic,
1255 and the second token is the filename of the keyring. Frequently a key
1256 tag may be given next, preceded by the token
1259 .BI "KEYMGMT private-keyring " file " key " tag " incorrect-public-key"
1260 The private key doesn't record the correct corresponding public key.
1262 .BI "KEYMGMT public-keyring " file " key " tag " algorithm-mismatch"
1263 A peer's public key doesn't request the same algorithms as our private
1266 .BI "KEYMGMT " which "-keyring " file " key " tag " bad-tag-length " len
1267 The key attributes specify the length of MAC tag as
1269 but this is an invalid value \(en either too large or not a multiple of
1272 .BI "KEYMGMT " which "-keyring " file " key " tag " bad-tag-length-string " str
1273 The key attributes contain
1275 where a MAC tag length was expected. The key was generated wrongly.
1277 .BI "KEYMGMT private-keyring " file " key " tag " changed-group"
1278 The private keyring has been changed, but the new private key can't be
1279 used because it uses a different group for Diffie\(enHellman key
1282 .BI "KEYMGMT " which "-keyring " file " io-error " ecode " " message
1283 A system error occurred while opening or reading the keyring file.
1285 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-bulk-transform " bulk
1286 The key specifies the use of an unknown bulk-crypto transform
1288 Maybe the key was generated wrongly, or maybe the version of Catacomb
1289 installed is too old.
1291 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-cipher " cipher
1292 The key specifies the use of an unknown symmetric encryption algorithm
1294 Maybe the key was generated wrongly, or maybe the version of
1295 Catacomb installed is too old.
1297 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-group-type " type
1298 The key specifies the use of a Diffie\(enHellman group of an unknown
1300 Maybe the key was generated wrongly, or maybe the version of
1304 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-hash " hash
1305 The key specifies the use of an unknown hash function
1307 Maybe the key was generated wrongly, or maybe the version of Catacomb
1308 installed is too old.
1310 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-mac " mac
1311 The key specifies the use of an unknown message authentication code
1313 Maybe the key was generated wrongly, or maybe the version of Catacomb
1314 installed is too old.
1316 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-mgf-cipher " mgf
1317 The key specifies the use of an unknown symmetric encryption function
1319 for mask generation. Maybe the key was generated wrongly, or maybe the
1320 version of Catacomb installed is too old.
1322 .BI "KEYMGMT " which "-keyring " file " key " tag " unknown-serialization-format " ser
1323 The key specifies the use of an unknown serialization format
1325 for hashing group elements. Maybe the key was generated wrongly, or
1326 maybe the version of Catacomb installed is too old.
1328 .BI "KEYMGMT " which "-keyring " file " key " tag " no-hmac-for-hash " hash
1329 No message authentication code was given explicitly, and there's no
1330 implementation of HMAC for the selected hash function
1333 .BI "KEYMGMT " which "-keyring " file " key " tag " " alg " " name " no-key-size " hashsz
1340 The named algorithm requires more key material than the hash function
1341 can provide. You must change either the hash function, or the cipher or
1344 .BI "KEYMGMT " which "-keyring " file " key " tag " mgf " mgf " restrictive-key-schedule"
1345 The cipher selected for mask-generation is unsuitable because it can't
1346 accept arbitrary-sized keys.
1348 .BI "KEYMGMT " which "-keyring " file " key-not-found " tag
1351 couldn't be found in the keyring.
1353 .BI "KEYMGMT " which "-keyring " file " line " line " " message
1354 The contents of the keyring file are invalid. There may well be a bug
1359 These indicate problems during key-exchange. Many indicate either a bug
1360 in the server (either yours or the remote one), or some kind of attack
1361 in progress. All name a
1363 as the second token: this is the peer the packet is apparently from,
1364 though it may have been sent by an attacker instead.
1366 In the descriptions below,
1368 is one of the tokens
1377 .BI "KX " peer " algorithms-mismatch local-private-key " privtag " peer-public-key " pubtag
1378 The algorithms specified in the peer's public key
1380 don't match the ones described in the private key
1383 .BI "KX " peer " bad-expected-reply-log"
1386 uses in its protocol contain a check value which proves that the
1387 challenge is honest. This message indicates that the check value
1388 supplied is wrong: someone is attempting to use bogus challenges to
1391 server to leak private key information. No chance!
1393 .BI "KX " peer " decrypt-failed reply\fR|\fBswitch-ok"
1394 A symmetrically-encrypted portion of a key-exchange message failed to
1397 .BI "KX " peer " invalid " msgtoken
1398 A key-exchange message was malformed. This almost certainly indicates a
1401 .BI "KX " peer " incorrect cookie\fR|\fBswitch-rq\fR|\fBswitch-ok"
1402 A message didn't contain the right magic data. This may be a replay of
1403 some old exchange, or random packets being sent in an attempt to waste
1406 .BI "KX " peer " " which "-key-expired"
1407 The local private key or the peer's public key (distinguished by
1409 has expired. Either you or the peer's maintainer should have arranged
1410 for a replacement before now.
1412 .BI "KX " peer " sending-cookie"
1413 We've received too many bogus pre-challenge messages. Someone is trying
1414 to flood us with key-exchange messages and make us waste CPU on doing
1415 hard asymmetric crypto sums.
1417 .BI "KX " peer " unexpected " msgtoken
1418 The message received wasn't appropriate for this stage of the key
1419 exchange process. This may mean that one of our previous packets got
1422 it may simply mean that the peer has recently restarted.
1424 .BI "KX " peer " unknown-challenge"
1425 The peer is asking for an answer to a challenge which we don't know
1426 about. This may mean that we've been inundated with challenges from
1427 some malicious source
1428 .I who can read our messages
1429 and discarded the valid one.
1431 .BI "KX " peer " unknown-message 0x" nn
1432 An unknown key-exchange message arrived.
1434 These are largely concerned with management of peers and the low-level
1435 details of the network protocol. The second token is usually the name of
1438 if none is relevant.
1440 .BI "PEER " peer " bad-packet no-type"
1441 An empty packet arrived. This is very strange.
1443 .BI "PEER " peer " bad-packet unknown-category 0x" nn
1444 The message category
1446 (in hex) isn't understood. Probably a strange random packet from
1447 somewhere; could be an unlikely bug.
1449 .BI "PEER " peer " bad-packet unknown-type 0x" nn
1452 (in hex) isn't understood. Probably a strange random packet from
1453 somewhere; could be an unlikely bug.
1455 .BI "PEER " peer " corrupt-encrypted-ping"
1456 The peer sent a ping response which matches an outstanding ping, but its
1457 payload is wrong. There's definitely a bug somewhere.
1459 .BI "PEER " peer " corrupt-transport-ping"
1460 The peer (apparently) sent a ping response which matches an outstanding
1461 ping, but its payload is wrong. Either there's a bug, or the bad guys
1462 are playing tricks on you.
1464 .BI "PEER " peer " decrypt-failed"
1465 An encrypted IP packet failed to decrypt. It may have been mangled in
1466 transit, or may be a very old packet from an expired previous session
1467 key. There is usually a considerable overlap in the validity periods of
1468 successive session keys, so this shouldn't occur unless the key exchange
1469 takes ages or fails.
1471 .BI "PEER " peer " malformed-encrypted-ping"
1472 The peer sent a ping response which is hopelessly invalid. There's
1473 definitely a bug somewhere.
1475 .BI "PEER " peer " malformed-transport-ping"
1476 The peer (apparently) sent a ping response which is hopelessly invalid.
1477 Either there's a bug, or the bad guys are playing tricks on you.
1479 .BI "PEER " peer " packet-build-failed"
1480 There wasn't enough space in our buffer to put the packet we wanted to
1481 send. Shouldn't happen.
1483 .BI "PEER \- socket-read-error " ecode " " message
1484 An error occurred trying to read an incoming packet.
1486 .BI "PEER " peer " socket-write-error " ecode " " message
1487 An error occurred attempting to send a network packet. We lost that
1490 .BI "PEER " peer " unexpected-encrypted-ping 0x" id
1491 The peer sent an encrypted ping response whose id doesn't match any
1492 outstanding ping. Maybe it was delayed for longer than the server was
1493 willing to wait, or maybe the peer has gone mad.
1495 .BI "PEER \- unexpected-source " address\fR...
1496 A packet arrived from
1498 (a network address \(en see above), but no peer is known at that
1499 address. This may indicate a misconfiguration, or simply be a result of
1500 one end of a connection being set up before the other.
1502 .BI "PEER " peer " unexpected-transport-ping 0x" id
1503 The peer (apparently) sent a transport ping response whose id doesn't
1504 match any outstanding ping. Maybe it was delayed for longer than the
1505 server was willing to wait, or maybe the peer has gone mad; or maybe
1506 there are bad people trying to confuse you.
1507 .SS "SERVER warnings"
1508 These indicate problems concerning the server process as a whole.
1510 .BI "SERVER ignore signal " name
1511 A signal arrived, but the server ignored it. Currently this happens for
1513 because that's a popular way of telling daemons to re-read their
1514 configuration files. Since
1516 re-reads its keyrings automatically and has no other configuration
1517 files, it's not relevant, but it seemed better to ignore the signal than
1520 .BI "SERVER quit signal " \fR[\fInn\fR|\fIname\fR]
1521 A signal arrived and
1525 .BI "SERVER quit admin-request"
1526 A client of the administration interface issued a
1530 .BI "SERVER quit foreground-eof"
1531 The server is running in foreground mode (the
1533 option), and encountered end-of-file on standard input.
1535 .BI "SERVER select-error " ecode " " message
1536 An error occurred in the server's main event loop. This is bad: if it
1537 happens too many times, the server will abort.
1539 These are concerned with the symmetric encryption and decryption
1542 .BI "SYMM replay old-sequence"
1543 A packet was received with an old sequence number. It may just have
1544 been delayed or duplicated, or it may have been an attempt at a replay
1547 .BI "SYMM replay duplicated-sequence"
1548 A packet was received with a sequence number we've definitely seen
1549 before. It may be an accidental duplication because the 'net is like
1550 that, or a deliberate attempt at a replay.
1552 These concern the workings of the system-specific tunnel driver. The
1553 second token is the name of the tunnel interface in question, or
1557 .BI "TUN \- bsd no-tunnel-devices"
1558 The driver couldn't find an available tunnel device. Maybe if you
1561 files, it will work.
1563 .BI "TUN \- " tun-name " open-error " device " " ecode " " message
1564 An attempt to open the tunnel device file
1568 .BI "TUN \- linux config-error " ecode " " message
1569 Configuring the Linux TUN/TAP interface failed.
1571 .BI "TUN " ifname " " tun-name " read-error " ecode " " message
1572 Reading from the tunnel device failed.
1574 .BI "TUN " ifname " " tun-name " write-error " ecode " " message
1575 Writing from the tunnel device failed.
1577 .BI "TUN " ifname " slip bad-escape"
1578 The SLIP driver encountered a escaped byte it wasn't expecting to see.
1579 The erroneous packet will be ignored.
1581 .BI "TUN " ifname " slip eof"
1582 The SLIP driver encountered end-of-file on its input descriptor.
1583 Pending data is discarded, and no attempt is made to read any more data
1584 from that interface ever.
1586 .BI "TUN " ifname " slip escape-end"
1587 The SLIP driver encountered an escaped `end' marker. This probably
1588 means that someone's been sending it junk. The erroneous packet is
1589 discarded, and we hope that we've rediscovered synchronization.
1591 .BI "TUN \- slip fork-error " ecode " " message
1592 The SLIP driver encountered an error forking a child process while
1593 allocating a new dynamic interface.
1595 .BI "TUN \- slip no-slip-interfaces"
1596 The driver ran out of static SLIP interfaces. Either preallocate more,
1597 or use dynamic SLIP interface allocation.
1599 .BI "TUN " ifname " slip overflow"
1600 The SLIP driver gave up reading a packet because it got too large.
1602 .BI "TUN \- slip pipe-error " ecode " " message
1603 The SLIP driver encountered an error creating pipes while allocating a
1604 new dynamic interface.
1606 .BI "TUN \- slip read-ifname-failed " ecode " " message
1607 The SLIP driver encountered an error reading the name of a dynamically
1608 allocated interface. Maybe the allocation script is broken.
1610 .BI "TUN \- unet config-error " ecode " " message
1611 Configuring the Linux Unet interface failed. Unet is obsolete and
1612 shouldn't be used any more.
1614 .BI "TUN \- unet getinfo-error " ecode " " message
1615 Reading information about the Unet interface failed. Unet is obsolete
1616 and shouldn't be used any more.
1618 These are issued by administration clients using the
1622 .BI "USER " tokens\fR...
1623 An administration client issued a warning.
1626 .\"--------------------------------------------------------------------------
1629 .SS "Command responses"
1632 .BI "BGFAIL " tag " " tokens \fR...
1633 .BI "BGINFO " tag " " tokens \fR...
1635 .BI "FAIL " tokens \fR...
1636 .BI "INFO " tokens \fR...
1641 .\"--------------------------------------------------------------------------
1647 .IR "The Trivial IP Encryption Protocol" .
1649 .\"--------------------------------------------------------------------------
1652 Mark Wooding, <mdw@distorted.org.uk>
1654 .\"----- That's all, folks --------------------------------------------------
~mdw / tripe / blob