summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJameson Graef Rollins <jrollins@phys.columbia.edu>2008-05-26 18:56:10 -0400
committerJameson Graef Rollins <jrollins@phys.columbia.edu>2008-05-26 18:56:10 -0400
commit2d330bf026a4986e85b65e77fc6bf27df70d02bc (patch)
treef450b0a511e22f1f25fce88b4318058c4e0a09c6 /doc
parent84d5807bec33e8f5e7ef8de8c9488c5895bdd838 (diff)
update README to reflect changes to howler trust-key
Diffstat (limited to 'doc')
-rw-r--r--doc/README9
1 files changed, 3 insertions, 6 deletions
diff --git a/doc/README b/doc/README
index 9034519..d8f1897 100644
--- a/doc/README
+++ b/doc/README
@@ -61,13 +61,10 @@ that user. However, in order for users to become authenticated, the
server must determine that the user keys have "full" validity. This
means that the server must fully trust at least one person whose
signature on the connecting users key would validate the user. This
-would generally be the server admin. If the server admin's userid is
+would generally be the server admin. If the server admin's keyid is
+XXXXXXXX, then on the server run:
-"Alice <alice@foo.com>"
-
-then the server would run:
-
-# howler trust-uids "Alice <alice@foo.com>"
+# howler trust-key XXXXXXXX
To update the ms authorized_keys file for user "bob", the system would
then run the following: