098-todo.txt 2.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576
  1. Filename: 098-todo.txt
  2. Title: Proposals that should be written
  3. Version: $Revision$
  4. Last-Modified: $Date$
  5. Author: Nick Mathewson, Roger Dingledine
  6. Created:
  7. Overview:
  8. This document lists ideas that various people have had for improving the
  9. Tor protocol. These should be implemented and specified if they're
  10. trivial, or written up as proposals if they're not.
  11. This is an active document, to be edited as proposals are written and as
  12. we come up with new ideas for proposals. We should take stuff out as it
  13. seems irrelevant.
  14. For protocol version 2:
  15. - Fix onionskin handshake scheme to be more mainstream, less nutty.
  16. Can we just do
  17. E(HMAC(g^x), g^x) rather than just E(g^x) ?
  18. No, that has the same flaws as before. We should send
  19. E(g^x, C) with random C and expect g^y, HMAC_C(K=g^xy).
  20. Better ask Ian; probably Stephen too.
  21. - Versioned CREATE and friends
  22. - Length on CREATE and friends
  23. - Versioning on circuits
  24. - Versioning on create cells
  25. - SHA1 is showing its age
  26. - Not being able to upgrade ciphersuites or increase key lengths is
  27. lame.
  28. Any time:
  29. - REASON_CONNECTFAILED should include an IP.
  30. - Spec should incorporate some prose from tor-design to be more readable.
  31. - Spec when we should rotate which keys
  32. Things that should change...
  33. B.1. ... but which will require backward-incompatible change
  34. - Circuit IDs should be longer.
  35. - IPv6 everywhere.
  36. - Maybe, keys should be longer.
  37. - Maybe, key-length should be adjustable. How to do this without
  38. making anonymity suck?
  39. - Drop backward compatibility.
  40. - We should use a 128-bit subgroup of our DH prime.
  41. - Handshake should use HMAC.
  42. - Multiple cell lengths.
  43. - Ability to split circuits across paths (If this is useful.)
  44. - SENDME windows should be dynamic.
  45. - Directory
  46. - Stop ever mentioning socks ports
  47. B.1. ... and that will require no changes
  48. - Mention multiple addr/port combos
  49. - Advertised outbound IP?
  50. - Migrate streams across circuits.
  51. B.2. ... and that we have no idea how to do.
  52. - UDP (as transport)
  53. - UDP (as content)
  54. - Use a better AES mode that has built-in integrity checking,
  55. doesn't grow with the number of hops, is not patented, and
  56. is implemented and maintained by smart people.
  57. Let onion keys be not just RSA but maybe DH too. for the reply onion
  58. design.