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
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.
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.
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.
+
+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.
-When using ssh-proxycommand, if only host keys found are expired or
- revoked, then output loud warning with prompt, or fail hard.
+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.
projects / monkeysphere.git / blobdiff