X-Git-Url: https://codewiz.org/gitweb?a=blobdiff_plain;f=doc%2FTODO;h=8be02b93811ea2a23fa324ef10f942429e84690f;hb=644d0d7a37aa265dfbdc15ba565323a005130823;hp=a82f031dd96dbe61048e638cf875a856e1125eca;hpb=f659da8ba2e184a9eb60da2d65c1e81c33f06772;p=monkeysphere.git diff --git a/doc/TODO b/doc/TODO index a82f031..8be02b9 100644 --- a/doc/TODO +++ b/doc/TODO @@ -5,9 +5,6 @@ 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. -Determine how openssh handles multiple processes writing to - known_hosts/authorized_keys files (lockfile, atomic appends?) - 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? @@ -30,22 +27,10 @@ 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 + /var/lib/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. @@ -56,8 +41,10 @@ Provide a friendly interactive UI for marginal or failing client-side 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. @@ -93,17 +80,30 @@ File bug against ssh-keygen about how "-R" option removes comments File bug against ssh-keygen to see if we can get it to write to hash a known_hosts file to/from stdout/stdin. -Add environment variables sections to man pages. +When using ssh-proxycommand, if only host keys found are expired or + revoked, then output loud warning with prompt, or fail hard. -Environment variable scoping. +File bug against seahorse about how, when creating new primary keys, + it presents option for "RSA (sign only)" but then creates an "esca" + key. -Move environment variable precedence before conf file. +File bug against enigmail about lack of ability to create subkeys. -When using ssh-proxycommand, if only host keys found are expired or - revoked, then output loud warning with prompt, or fail hard. +Test and document what happens when any filesystem that the + monkeysphere-server relies on and modifies (/tmp, /etc, and /var?) + fills up. + +Optimize keyserver access, particularly on monkeysphere-server + update-users -- is there a way to query the keyserver all in a + chunk? + +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. +Add "monkeysphere-server diagnostics" subcommand to identify missing + pieces of monkeysphere server administration setup.