See proposal 289 section 4.5 which is about adding a consensus param that controls the minimum version to use when doing one-hop directory connections.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items 0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items 0
Link issues together to show that they're related.
Learn more.
The "onehop" concept was dropped because it is actually not reliable to figure that out but also it doesn't matter if we have a 3 hop or 1 hop I believe.
In the end, any directory requests on a circuit will result in honoring this SENDME version from the consensus param. It is actually hard to associate a circuit to a hidden service directory request at the server side. Not impossible but hard.
Trac: Actualpoints: N/Ato 0.2 Status: assigned to needs_review
Interesting... I have one question there that will drive quite a bit how everything else is fixed. Once that is clarified, I might just submit an _02 since like more than 50% of the patch will change... Thanks!
After discussion with nickm on IRC, we'll drop this idea and instead go with this deployment plan:
emit=v1, accept=v0, protover=v0
emit=v1, accept=v0, protover=v1
emit=v1, accept=v1, protover=v1
Bottom line is that during phase 2, we will exit() all tor that do not support SENDME >= v1 but still accept v0 so bootstrapping tor can learn what is required. Finally, phase 3 will stop all this madness and normalize everyone to v1.
This mean that we'll drop this ticket entirely. I've opened #30557 (moved) for the change on the spec.
Trac: Resolution: N/Ato wontfix Status: needs_revision to closed