summaryrefslogtreecommitdiff
path: root/doc/TODO
blob: 733986e102224cb374510c2cf46adc367381a310 (plain)
  1. Next-Steps Monkeysphere Projects:
  2. ---------------------------------
  3. Detail advantages of monkeysphere: detail the race conditions in ssh,
  4. and how the monkeysphere can help you reduce these threat vectors:
  5. threat model reduction diagrams.
  6. Handle unverified monkeysphere hosts in such a way that they're not
  7. always removed from known_hosts file. Ask user to lsign the host
  8. key?
  9. Work out the details (and describe a full use case) for assigning a
  10. REVOKER during monkeysphere-server gen_key -- how is this set? How
  11. do we export it so it's available when a second-party revocation is
  12. needed?
  13. Ensure that authorized_user_ids are under as tight control as ssh
  14. expects from authorized_keys: we don't want monkeysphere to be a
  15. weak link in the filesystem.
  16. Consider the default permissions for
  17. /var/lib/monkeysphere/authorized_keys/* (and indeed the whole
  18. directory path leading up to that)
  19. Make sure alternate ports are handled for known_hosts.
  20. Script to import private key into ssh agent.
  21. Provide a friendly interactive UI for marginal or failing client-side
  22. hostkey verifications. Handle the common cases smoothly, and
  23. provide good debugging info for the unusual cases.
  24. Make sure onak properly escapes user IDs with colons in them.
  25. Indicate on web site how to report trouble or concerns, and how to
  26. join the project.
  27. Clean up the style for the web site (pages, icons, etc).
  28. Create ssh2openpgp or convert to full-fledged keytrans.
  29. Resolve the bugs listed in openpgp2ssh(1):BUGS.
  30. Document alternate trustdb models.
  31. Understand and document the output of gpg --check-trustdb:
  32. gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
  33. gpg: depth: 0 valid: 2 signed: 20 trust: 0-, 0q, 0n, 0m, 0f, 2u
  34. gpg: depth: 1 valid: 20 signed: 67 trust: 15-, 0q, 1n, 3m, 1f, 0u
  35. gpg: next trustdb check due at 2008-10-09
  36. Understand and document the numeric values between sig! and the keyid
  37. in "gpg --check-sigs $KEYID" . Compare with the details found from
  38. "gpg --with-colons --check-sigs $KEYID". This has to do with trust
  39. signatures.
  40. Fix gpg's documentation to clarify the difference between validity and
  41. ownertrust. Include better documentation for trust signatures.
  42. Make it easier to do domain-relative ssh host trust signatures with
  43. gnupg. (e.g. "i trust Jamie McClelland (keyID 76CC057D) to properly
  44. identify ssh servers in the mayfirst.org domain") See:
  45. http://tools.ietf.org/html/rfc4880#section-5.2.3.21 and grep for
  46. "tsign" in gpg(1).
  47. Fix the order of questions when user does a tsign in gpg or gpg2.
  48. File bug against ssh-keygen about how "-R" option removes comments
  49. from known_hosts file.
  50. File bug against ssh-keygen to see if we can get it to write to hash a
  51. known_hosts file to/from stdout/stdin.
  52. When using ssh-proxycommand, if only host keys found are expired or
  53. revoked, then output loud warning with prompt, or fail hard.
  54. File bug against seahorse about how, when creating new primary keys,
  55. it presents option for "RSA (sign only)" but then creates an "esca"
  56. key.
  57. File bug against enigmail about lack of ability to create subkeys.
  58. Test and document what happens when any filesystem that the
  59. monkeysphere-server relies on and modifies (/tmp, /etc, and /var?)
  60. fills up.
  61. Optimize keyserver access, particularly on monkeysphere-server
  62. update-users -- is there a way to query the keyserver all in a
  63. chunk?
  64. Create DSA authentication subkey for server during gen-key
  65. Fix behavior when add-identity-certifier fails to fetch a key from the
  66. keyserver.
  67. Allow server administrators to add-identity-certifier from a key in
  68. the filesystem (or on stdin, etc)