re-worked documentation and raised issues in TODO about end user authentication.

diff --git a/doc/TODO b/doc/TODO
index e2fce0e8f7a10f45f4cd43751a835d81a13b905c..5cd9be9cb8784521e652237e484e53fe7376a399 100644 (file)
--- a/doc/TODO
+++ b/doc/TODO
@@ -35,6 +35,32 @@ Ensure that authorized_user_ids are under as tight control as ssh
    expects from authorized_keys: we don't want monkeysphere to be a
    weak link in the filesystem.
 
+What happens when there are no entries in the authorized_user_ids file
+   for a user?  /var/cache/monkeysphere/authorized_keys/$USER.tmp
+   seems like it gets created and then left there.
+
+What happens when a user account has no corresponding
+   /etc/monkeysphere/authorized_user_ids/$USER file?  What gets placed
+   in /var/cache/monkeysphere/authorized_keys/$USER?  It looks
+   currently untouched, which could mean bad things for such a user.
+
+Consider the default permissions for
+   /var/cache/monkeysphere/authorized_keys/* (and indeed the whole
+   directory path leading up to that)
+
+What should happen when an admin does 
+   "monkeysphere-server update-users not_an_existent_user"?
+   currently, it adds
+   /etc/monkeysphere/authorized_user_ids/not_an_existent_user, which
+   seems rather wrong.
+
+is /var/cache/monkeysphere/authorized_keys/$USER.tmp guaranteed to
+   avoid collisions?  Why not use a real mktemp file?
+
+As an administrator, how do i reverse the effect of a
+   "monkeysphere-server trust-keys" that i later decide i should not
+   have run?
+
 Make sure alternate ports are handled for known_hosts.
 
 Script to import private key into ssh agent.

diff --git a/doc/george/user-id-configuration b/doc/george/user-id-configuration
index d95279df627b2398c9b58297becd7bd85cebf596..d42bfbd1c05730299d0be6dfa0d8dc03b7013ec2 100644 (file)
--- a/doc/george/user-id-configuration
+++ b/doc/george/user-id-configuration
@@ -4,18 +4,44 @@
 setting up authorized_user_id configuration on george was also more
 cumbersome than it needs to be.  Here's what i (dkg) did:
 
- GNUPGHOME=/etc/monkeysphere/gnupg gpg --keyserver subkeys.pgp.net --search dkg@fifthhorseman.net
- GNUPGHOME=/etc/monkeysphere/gnupg gpg --fingerprint dkg@fifthhorseman.net
-
-set up the authorized_user_ids (why are these in /etc/ and not in
-people's home directories?)
-
-echo 'Daniel Kahn Gillmor <dkg@fifthhorseman.net>' > /etc/monkeysphere/authorized_user_ids/dkg
-echo 'Jameson Rollins <jrollins@fifthhorseman.net>' > /etc/monkeysphere/authorized_user_ids/jrollins
-echo 'Micah Anderson <micah@riseup.net>' > /etc/monkeysphere/authorized_user_ids/micah
-echo 'Matthew Goins <mjgoins@openflows.com>' > /etc/monkeysphere/authorized_user_ids/mjgoins
-echo 'Ross Glover <ross@ross.mayfirst.org>' > /etc/monkeysphere/authorized_user_ids/ross
-echo 'Jamie McClelland <jamie@mayfirst.org>' > /etc/monkeysphere/authorized_user_ids/jamie
-echo 'mike castleman <m@mlcastle.net>' > /etc/monkeysphere/authorized_user_ids/mlcastle
-echo 'Elliot Winard <enw@caveteen.com>' > /etc/monkeysphere/authorized_user_ids/enw
-echo 'Greg Lyle <greg@stealthisemail.com>' > /etc/monkeysphere/authorized_user_ids/greg
+monkeysphere-server trust-keys 0EE5BE979282D80B9F7540F1CCD2ED94D21739E9
+
+monkeysphere-server update-user-userids dkg 'Daniel Kahn Gillmor <dkg@fifthhorseman.net>'
+monkeysphere-server update-user-userids jrollins 'Jameson Rollins <jrollins@fifthhorseman.net>'
+monkeysphere-server update-user-userids micah 'Micah Anderson <micah@riseup.net>' 
+monkeysphere-server update-user-userids mjgoins 'Matthew Goins <mjgoins@openflows.com>'
+monkeysphere-server update-user-userids ross 'Ross Glover <ross@ross.mayfirst.org>'
+monkeysphere-server update-user-userids jamie 'Jamie McClelland <jamie@mayfirst.org>'
+monkeysphere-server update-user-userids mlcastle 'mike castleman <m@mlcastle.net>'
+monkeysphere-server update-user-userids enw 'Elliot Winard <enw@caveteen.com>'
+monkeysphere-server update-user-userids greg 'Greg Lyle <greg@stealthisemail.com>' 
+
+
+then i added a scheduled:
+
+  monkeysphere-server update-users
+
+to run hourly via /etc/crontab
+
+and made sure that root's keys were working with a temporary symlink
+(see TODO about that business)
+
+and then modified /etc/ssh/sshd_config with:
+
+ AuthorizedKeysFile      /var/cache/monkeysphere/authorized_keys/%u
+
+
+Some outstanding questions:
+
+ * why are the authorized_user_ids stored in /etc/ and not in people's
+   home directories?
+
+ * why are authorized_user_ids managed with a special sub-command of
+   monkeysphere-server, instead of just being hand-managed files, the
+   way that authorized_keys are in stock openssh?
+
+ * Should we ship a scheduled monkeysphere-server update-users cron
+   job automatically?
+
+ * why was i not prompted to confirm the trust-keys line, which seems
+   like the most delicate/sensitive line of all of them?