server/peer.c, etc.: Introduce who-goes-there protocol.

[tripe] / server / tripe-admin.5.in

diff --git a/server/tripe-admin.5.in b/server/tripe-admin.5.in
index 3e7bd8e..ea2183c 100644 (file)
--- a/server/tripe-admin.5.in
+++ b/server/tripe-admin.5.in
@@ -1365,6 +1365,16 @@ is no longer available.
 An administration client issued a notification using the
 .B NOTIFY
 command.
+.SP
+.BI "WGT " peer
+A who-goes-there message was received from an ephemeral
+.IR peer ,
+implying that it has forgotten about us.  If a service knows how to
+inform the peer of our existence, it should do so.  This notification is
+not sent for peers which have a
+.B knock
+string configured, because the server automatically tries knocking again
+in this case.
 .
 .\"--------------------------------------------------------------------------
 .SH "WARNINGS"
@@ -1837,6 +1847,17 @@ The peer (apparently) sent a transport ping response whose id doesn't
 match any outstanding ping.  Maybe it was delayed for longer than the
 server was willing to wait, or maybe the peer has gone mad; or maybe
 there are bad people trying to confuse you.
+.SP
+.BI "PEER " peer " unexpected-wgt"
+A `who-goes-there' message from received from
+.IR peer ,
+but the peer isn't ephemeral.
+.SP
+.BI "PEER " peer " unrecognized-wgt"
+A `who-goes-there' message from received from
+.IR peer ,
+but it doesn't quote the start of a message which we recently sent to
+it.
 .SS "PRIVSEP warnings"
 These indicate problems with the privilege-separation helper process.
 (The server tries to drop its privileges when it starts up, leaving a