X-Git-Url: https://codewiz.org/gitweb?a=blobdiff_plain;f=doc%2FTODO;h=6006d628b5820b4a5681800380fd25c0c25d3b75;hb=52287b8dcbbf89b2df82c314e8c564de87a20234;hp=5cd9be9cb8784521e652237e484e53fe7376a399;hpb=86e9e0e3fd03db1770857990882d955954a5265b;p=monkeysphere.git

diff --git a/doc/TODO b/doc/TODO
index 5cd9be9..6006d62 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -5,16 +5,10 @@ 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?
 
-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
@@ -26,41 +20,14 @@ Streamline host key generation, publication, verification.  See
    doc/george/host-key-publication for what dkg went through on
    2008-06-19
 
-Streamline authorized_user_ids setup (including question of where
-   authorized_user_ids files should go).  See
-   doc/george/user-id-configuration 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 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
+   /var/lib/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.
@@ -71,8 +38,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.
 
@@ -108,17 +77,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.