Next-Steps Monkeysphere Projects:
---------------------------------
-Handle unknown hosts in such a way that they're not always removed
- from known_hosts file. Ask user to lsign the host key?
+Detail advantages of monkeysphere: detail the race conditions in ssh,
+ and how the monkeysphere can help you reduce these threat vectors:
+ threat model reduction diagrams.
-Handle multiple hostnames (multiple user IDs?) when generating host
- keys with gen-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?
+
+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?
+
+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.
+
+Consider the default permissions for
+ /var/lib/monkeysphere/authorized_keys/* (and indeed the whole
+ directory path leading up to that)
Make sure alternate ports are handled for known_hosts.
Make sure onak properly escapes user IDs with colons in them.
-Build a decent, presentable web site for documentation, evangelism,
- etc. Include a mention of how to report trouble or concerns.
+Indicate on web site how to report trouble or concerns, and how to
+ join the project.
+
+Clean up the style for the web site (pages, icons, etc).
Create ssh2openpgp or convert to full-fledged keytrans.
Resolve the bugs listed in openpgp2ssh(1):BUGS.
-Understand and document alternate trustdb models.
+Document alternate trustdb models.
Understand and document the output of gpg --check-trustdb:
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
File bug against ssh-keygen to see if we can get it to write to hash a
known_hosts file to/from stdout/stdin.
-Note all threat model reductions (with diagrams).
+When using ssh-proxycommand, if only host keys found are expired or
+ revoked, then output loud warning with prompt, or fail hard.
-Add environment variables sections to man pages.
+File bug against seahorse about how, when creating new primary keys,
+ it presents option for "RSA (sign only)" but then creates an "esca"
+ key.
-Environment variable scoping.
+File bug against enigmail about lack of ability to create subkeys.
-Move environment variable precedence before conf file.
+Test and document what happens when any filesystem that the
+ monkeysphere-server relies on and modifies (/tmp, /etc, and /var?)
+ fills up.
-Handle lockfiles when modifying known_hosts or authorized_keys.
+Optimize keyserver access, particularly on monkeysphere-server
+ update-users -- is there a way to query the keyserver all in a
+ chunk?
-When using ssh-proxycommand, if only host keys found are expired or
- revoked, then output loud warning with prompt, or fail hard.
+Create DSA authentication subkey for server during gen-key
+
+Fix behavior when add-identity-certifier fails to fetch a key from the
+ keyserver.
-Update monkeysphere-ssh-proxycommand man page with new keyserver
- checking policy info.
+Allow server administrators to add-identity-certifier from a key in
+ the filesystem (or on stdin, etc)
-Update monkeysphere-ssh-proxycommand man page with info about
- no-connect option.
+Think about packaging monkeysphere for other (non-apt-based) operating
+ systems. RPM-based linux systems, FreeBSD ports, and Mac OS X seem
+ like the most likely candidates.