summaryrefslogtreecommitdiff
path: root/doc/TODO
diff options
context:
space:
mode:
Diffstat (limited to 'doc/TODO')
-rw-r--r--doc/TODO26
1 files changed, 26 insertions, 0 deletions
diff --git a/doc/TODO b/doc/TODO
index e2fce0e..5cd9be9 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -35,6 +35,32 @@ 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
+ 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.