Determine how openssh handles multiple processes writing to
known_hosts/authorized_keys files (lockfile, atomic appends?)
-Handle unknown hosts in such a way that they're not always removed
- from known_hosts file. Ask user to lsign the host key?
+Handle unverified monkeysphere hosts in such a way that they're not
+ always removed from known_hosts file. Ask user to lsign the host
+ key?
Handle multiple hostnames (multiple user IDs?) when generating host
keys with gen-key.
+Work out the details (and describe a full use case) for assigning a
+ REVOKER during monkeysphere-server gen_key -- how is this set? How
+ do we export it so it's available when a second-party revocation is
+ needed?
+
+Actually enable server hostkey publication.
+
+Streamline host key generation, publication, verification. See
+ doc/george/host-key-publication for what dkg went through on
+ 2008-06-19
+
+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 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.
+ - if authorized_user_ids is empty, then the user's authorized_keys
+ file will be also, unless the user-controlled authorized_keys file
+ is added. I believe this is expected, correct behavior.
+
+Consider the default permissions for
+ /var/cache/monkeysphere/authorized_keys/* (and indeed the whole
+ directory path leading up to that)
+
+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.
projects / monkeysphere.git / blobdiff