cryptographic directions in tor
play

Cryptographic directions in Tor Nick Mathewson nickm@torproject.org - PowerPoint PPT Presentation

Cryptographic directions in Tor Nick Mathewson nickm@torproject.org 6 Jan 2016 Outline W h e r e w e s t a r t e d Where we are Where we're going maybe. Let's oversimplify Tor, in 1 slide. L2 L3 Alice Alice K2 R2 L1 L1


  1. Cryptographic directions in Tor Nick Mathewson nickm@torproject.org 6 Jan 2016

  2. Outline ● W h e r e w e s t a r t e d ● Where we are ● Where we're going – maybe.

  3. Let's oversimplify Tor, in 1 slide. L2 L3 Alice Alice K2 R2 L1 L1 K1 K1 K2 K2 K3 K3 R3 L3 K3 R1 L1 L2 Bob K1

  4. We chose some reasonable-looking crypto in 2004... ● Relay encryption: AES-CTR + Truncated SHA1 – E n d - t o - e n d o n l y ● Key negotiation: “TAP”. – (RSA1024 + DH1024 + AES-CTR) ● Links: TLS1.0 – With DH1024, RSA1024, AES-CBC, SHA1.

  5. ...and we've replaced a lot of it... ● Relay encryption: AES-CTR + Truncated SHA1 – End-to-end only ● Key negotiation: “TAP” “ntor” – (RSA1024 + DH1024 + AES-CTR) – Curve25519 + SHA256 ● Links: TLS1.0 – With DH1024, RSA1024, AES-CBC, SHA1.

  6. ...and we've replaced a lot of it... ● Relay encryption: AES-CTR + Truncated SHA1 – End-to-end only ● Key negotiation: “TAP” “ntor” – (RSA1024 + DH1024 + AES-CTR) – Curve25519 + SHA256 ● Links: TLS1.0 TLS >= 1.0... – With DH1024, RSA1024, AES-CBC, SHA1. – With ECDH (P256), RSA1024, AES-GCM

  7. But work remains! ● Relay encryption: AES-CTR + Truncated SHA1 – End-to-end only Too Malleable! ● Key negotiation: “TAP” “ntor” Not – (RSA1024 + DH1024 + AES-CTR) Postquantum – Curve25519 + SHA256 Enough! ● Links: TLS1.0 TLS >= 1.0... – With DH1024, RSA1024, AES-CBC, SHA1. – With ECDH (P256), RSA1024, AES-GCM Just no.

  8. Malleable AES-CTR + end-to-end MAC allows tagging attacks. Alice Alice R2 Recovers plaintext, and finds data. Evil R3 Evil R1 Bob XORs data into ciphertext

  9. Solution: Add a MAC at each hop? Alice Alice Rejects ciphertext. R2 Observes: Evil Circuit closed. R3 Evil R1 Bob XORs data into ciphertext

  10. Solution: Add a MAC at each hop? Alice Alice Rejects ciphertext. R2 Evil R3 Evil R1 Bob XORs data into ciphertext

  11. But that leaks path length/position. Alice Alice R2 Smaller cells here! Big cells here! R3 R1 Bob

  12. Solution: Chained wide-block SPRP? Alice Alice Garbled ciphertext R2 Observes: Evil Circuit garbled. R3 Evil R1 Bob XORs data into ciphertext

  13. Single anonymity tool seeks SPRP for good times, encryption. ● AEZ? (rogaway et al) – CAESAR candidate – Based on AES round function—complex. – Fast with AESNI; less so if not?? ● HHFHFH? (djb et al) – Feistel construction: simple, has proofs. – Instantiate with GF25519 / XChaCha20? – Slower than AEZ?? Need more data! ● Help?

  14. Also let's do PQ circuit extension! ● Forward secrecy matters most. ● Needs to be fast-ish and small-ish. ● No less secure than current ntor approach. (approximately:) – Alice → Bob: “g^x, Bob.” – Bob → Alice: “g^y, H1(g^xy, g^xb….)”. – Keys are: KDF(g^xy, g^xb….)

  15. Also let's do PQ circuit extension! ● Forward secrecy matters most. ● Needs to be fast-ish and small-ish. ● No less secure than current ntor approach. (approximately:) – Alice → Bob: “g^x, Bob, PQKey ” – Bob → Alice: “g^y, H1(g^xy, g^xb….), E(PQKey, N)”. – Keys are: KDF(g^xy, g^xb, N ….)

  16. Current candidates ● ntru? ● newhope? ● _________ ?

  17. Questions? ● Also see tor-dev mailing list for more discussion! ● Targeting 2016 deployment. ● Also, ask me about hidden service crypto.

Recommend


More recommend