Opened 8 years ago

Closed 5 years ago

#4436 closed defect (wontfix)

Bridges should be able to disable v1 and v2 link handshakes

Reported by: asn Owned by:
Priority: Medium Milestone: Tor: 0.2.6.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: maybe-proposal tor-bridge
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

There is no point in implementing scanning resistance and all that fancy stuff, if censors can make a bridge perform the fingerprintable v1/v2 link handshakes by adding a few ciphers to ClientHello, or renegotiating right after TLS.

There should be a way to disable v1 and v2 link handshakes before we implement scanning resistance stuff.

Child Tickets

Change History (8)

comment:1 Changed 8 years ago by nickm

This is going to need corresponding changes in advertising bridges (so you can say "I only support v3 and later handshakes") and in bridgedb (so you can say "It's okay to tell me about bridges that older Tors can't use.")

comment:2 Changed 8 years ago by nickm

Milestone: Tor: 0.2.4.x-final

Requires proposal; probably not trivial for 0.2.3. Marking for 0.2.4.

comment:3 Changed 7 years ago by nickm

Keywords: maybe-proposal added

comment:4 Changed 7 years ago by nickm

Keywords: tor-bridge added

comment:5 Changed 7 years ago by nickm

Component: Tor BridgeTor

comment:6 Changed 7 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final

comment:7 Changed 6 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.6.x-final

comment:8 Changed 5 years ago by andrea

Resolution: wontfix
Status: newclosed

Scanning resistance should happen by pluggable transports, and v1 and v2 should be deprecated.

Note: See TracTickets for help on using tickets.