Opened 6 years ago

Closed 6 years ago

#8561 closed enhancement (fixed)

Enable ntor protocol by default.

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: 0.2.4.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-client
Cc: karsten, mikeperry Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

It works for me, after all. Why not set the parameter to 1 in the consensuses, and to 1 in the configurations for 0.2.5?

Child Tickets

Change History (9)

comment:1 Changed 6 years ago by mikeperry

Cc: karsten mikeperry added

I think it would be a good idea to have torperf data on circuit failure rates (and the N most common remote+local REASON codes from the control port) during this transition. We expect that circuit failure rates should drop dramatically for ntor clients, and continue to drop as more clients upgrade to 0.2.4.x.

Confirmation of this fact could allow us to tighten the path bias parameters more. Right now they're rather ridiculously loose due to the high variability in CPU overload at relays.

karsten: We discussed this briefly at the dev meeting with Rob. Did you create a torperf ticket for it? I'd like to follow that one too.

comment:2 in reply to:  1 Changed 6 years ago by karsten

Replying to mikeperry:

karsten: We discussed this briefly at the dev meeting with Rob. Did you create a torperf ticket for it? I'd like to follow that one too.

See #8662.

comment:3 Changed 6 years ago by nickm

I'm turning this on-by-default in master. If nobody reports anything hinky in a week or so, I'll ask authority ops to start voting for it in the consensus so that 0.2.4 users get it too.

comment:4 Changed 6 years ago by nickm

(Done in 0124b10d2850c42e61a4ba65f61af579b47f425b)

comment:5 Changed 6 years ago by nickm

I have emailed the authorities.

(Wow, that sounds way more creepy than it is.)

comment:6 Changed 6 years ago by ioerror

I think this is a reasonable idea and I'm glad to see that we're moving forward with ntor!

My previous ConsensusParams were as follows:

ConsensusParams CircuitPriorityHalflifeMsec=30000 UseOptimisticData=1 bwauthpid=1 pb_disablepct=0

I've now set them to the following list:

ConsensusParams CircuitPriorityHalflifeMsec=30000 UseOptimisticData=1 bwauthpid=1 pb_disablepct=0 UseNTorHandshake=1

comment:7 Changed 6 years ago by ioerror

( I suppose that I'm the Man after being called an authority by nickm - who knew!)

comment:8 Changed 6 years ago by Sebastian

We have > 3 dirauths voting for the param from the next hour on

comment:9 Changed 6 years ago by andrea

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.