summaryrefslogtreecommitdiff
path: root/doc/TODO
diff options
context:
space:
mode:
authorJameson Graef Rollins <jrollins@phys.columbia.edu>2008-06-24 00:38:03 -0400
committerJameson Graef Rollins <jrollins@phys.columbia.edu>2008-06-24 00:38:03 -0400
commit7d02db7106da26f7705563297544a4ba1edfc71b (patch)
tree59a188d94a3a26c65cd0fc5010d4e39fed10d39b /doc/TODO
parent014bf21eae8b5358d0fc10c92c065e5a5deadab5 (diff)
Move to /var/lib/monkeysphere instead of /var/cache/monkeysphere.
Improve ms-server update-user function. Update/fix config files to remove some unwanted configs, and clarify some things.
Diffstat (limited to 'doc/TODO')
-rw-r--r--doc/TODO28
1 files changed, 1 insertions, 27 deletions
diff --git a/doc/TODO b/doc/TODO
index e1e90f0..e50da4d 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.
@@ -105,9 +90,6 @@ When using ssh-proxycommand, if only host keys found are expired or
Update monkeysphere-ssh-proxycommand man page with new keyserver
checking policy info.
-Update monkeysphere-ssh-proxycommand man page with info about
- no-connect option.
-
File bug against seahorse about how, when creating new primary keys,
it presents option for "RSA (sign only)" but then creates an "esca"
key.
@@ -118,18 +100,10 @@ Privilege separation: monkeysphere user to handle authn keyring and
generate authorized_keys file (which would be moved into place by
root). Host keyring would be owned by root.
-Check permissions of authorized_user_ids file to be writable only by
- user and root (same as authorized_keys)
-
-Improve function that sets owner trust for keys in server keychain.
-
Test and document what happens when any filesystem that the
monkeysphere-server relies on and modifies (/tmp, /etc, and /var?)
fills up.
-Consider moving monkeysphere-managed files (gpg homedirs? temporary
- files?) into /var.
-
Optimize keyserver access, particularly on monkeysphere-server
update-users -- is there a way to query the keyserver all in a
chunk?