1 2008-06-19 03:00:58-0400
2 ------------------------
4 setting up authorized_user_id configuration on george was also more
5 cumbersome than it needs to be. Here's what i (dkg) did:
7 monkeysphere-server trust-keys 0EE5BE979282D80B9F7540F1CCD2ED94D21739E9
9 monkeysphere-server update-user-userids dkg 'Daniel Kahn Gillmor <dkg@fifthhorseman.net>'
10 monkeysphere-server update-user-userids jrollins 'Jameson Rollins <jrollins@fifthhorseman.net>'
11 monkeysphere-server update-user-userids micah 'Micah Anderson <micah@riseup.net>'
12 monkeysphere-server update-user-userids mjgoins 'Matthew Goins <mjgoins@openflows.com>'
13 monkeysphere-server update-user-userids ross 'Ross Glover <ross@ross.mayfirst.org>'
14 monkeysphere-server update-user-userids jamie 'Jamie McClelland <jamie@mayfirst.org>'
15 monkeysphere-server update-user-userids mlcastle 'mike castleman <m@mlcastle.net>'
16 monkeysphere-server update-user-userids enw 'Elliot Winard <enw@caveteen.com>'
17 monkeysphere-server update-user-userids greg 'Greg Lyle <greg@stealthisemail.com>'
20 then i added a scheduled:
22 monkeysphere-server update-users
24 to run hourly via /etc/crontab
26 and made sure that root's keys were working with a temporary symlink
27 (see TODO about that business)
29 and then modified /etc/ssh/sshd_config with:
31 AuthorizedKeysFile /var/cache/monkeysphere/authorized_keys/%u
34 Some outstanding questions:
36 * why are the authorized_user_ids stored in /etc/ and not in people's
39 * why are authorized_user_ids managed with a special sub-command of
40 monkeysphere-server, instead of just being hand-managed files, the
41 way that authorized_keys are in stock openssh?
43 * Should we ship a scheduled monkeysphere-server update-users cron
46 * why was i not prompted to confirm the trust-keys line, which seems
47 like the most delicate/sensitive line of all of them?