keys/tripe-keys.8.in: Mention the `pathmtu' utility.

[tripe] / keys / tripe-keys.8.in

diff --git a/keys/tripe-keys.8.in b/keys/tripe-keys.8.in
index f94f968..353028e 100644 (file)
--- a/keys/tripe-keys.8.in
+++ b/keys/tripe-keys.8.in
@@ -27,7 +27,7 @@
 .so ../common/defs.man \" @@@PRE@@@
 .
 .\"--------------------------------------------------------------------------
-.TH tripe-keys 8 "14 September 2005" "Straylight/Edgeware" "TrIPE: Trivial IP Encryption"
+.TH tripe-keys 8tripe "14 September 2005" "Straylight/Edgeware" "TrIPE: Trivial IP Encryption"
 .
 .\"--------------------------------------------------------------------------
 .SH "NAME"
@@ -168,8 +168,12 @@ file.  Copy the results to the places named by
 .IR sig-file ,
 and
 .I conf-file
-respectively.  (This command is currently misnamed.  It only copies
-stuff about the local filesystem.  Some day it'll really upload stuff.)
+respectively.  Remove unexpected files from the
+.IR base-dir ,
+since these tend to be signatures made by old master keys which don't
+work any more.  Run the
+.I upload-hook
+to copy things into the right places.
 .TP
 .BI "generate " tag
 Generate a peer key for the peer named
@@ -236,7 +240,7 @@ TrIPE tunnel interface, given that the
 .I path-mtu
 between two peers is as specified.  The default is 1500, which is very
 commonly correct, but you should check using a tool such as
-.BR tracepath (8).
+.BR pathmtu (1).
 Getting the MTU too big will lead to unnecessary fragmentation of
 TrIPE's UDP datagrams; getting it too small will fail to utilize the
 underlying network effectively.  If in doubt, it's therefore better to