From 64b40a935427a48137efbf970bbc758fa19b643f Mon Sep 17 00:00:00 2001 From: Daniel Kahn Gillmor Date: Sun, 27 Jul 2008 16:08:16 -0400 Subject: [PATCH] updated README to explain why/when you might want to use update-authorized_keys. --- doc/README | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-) diff --git a/doc/README b/doc/README index e10f79b..bed0380 100644 --- a/doc/README +++ b/doc/README @@ -68,7 +68,12 @@ Miscellaneous ------------- Users can also maintain their own authorized_keys files, for users -that would be logging into their accounts. This is done with the +that would be logging into their accounts. This is primarily useful +for accounts on hosts that are not already systematically using the +monkeysphere for user authentication. If you're not sure whether this +is the case for your host, ask your system administrator. + +If you want to do this as a regular user, use the update-authorized_keys command: $ monkeysphere update-authorized_keys @@ -77,3 +82,10 @@ This command will take all the user IDs listed in the ~/.config/monkeysphere/authorized_user_ids file and check to see if there are acceptable keys for those user IDs available. If so, they will be added to the ~/.ssh/authorized_keys file. + +You must have indicated reasonable ownertrust in some key for this +account, or no keys will be found with trusted certification paths. + +If you find this useful, you might want to place a job like this in +your crontab so that revocations and rekeyings can take place +automatically. -- 2.25.1