#25662 closed defect (duplicate)

OBSOLETE OLD TOR CRYPTO AND ONLY RESOLVE OLD .ONION ADDRESSES

Reported by: Anony Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I think it would be best to completely obsolete all the old crypto within TOR, but if it is possible to only use it to resolve old .onion addresses and NOT to build new circuits EVER.

This would essentially be a firewall inside Tor to start only building circuits by default using the New Encryption introduced in Tor 0.3.2.9

There has been enough time elapsed for operators to upgrade and this is a serious bug if TOR is building obsolete circuits with obsolete TOR nodes. Thus the Default and Only setting should be to only build circuits using the Newer Encryption standard now that enough relays are already using the newer nodes.

Child Tickets

Change History (1)

comment:1 Changed 19 months ago by teor

Keywords: Upgraded Circuits TOR removed
Priority: ImmediateMedium
Resolution: duplicate
Severity: CriticalNormal
Status: newclosed
Version: Tor: unspecified

Tor has avoided using the legacy TAP protocol since 0.2.9, except when connection to v2 onion services.
We will obsolete v2 onion services when 0.2.9 is end of life in 2020, or maybe before that date.

There are already tickets for these changes.

Note: See TracTickets for help on using tickets.