MiddleOnly now means do not use as IP/RP.
Merge request reports
Activity
requested review from @dgoulet
assigned to @mikeperry
mentioned in commit 72ccd2e3
634 634 * **`HSDir`** --- is considered a v2 hidden service directory. 635 635 * **`MiddleOnly`** --- is considered unsuitable for usage 636 636 other than as a middle relay. 637 Clients do not need to handle this option, 638 since when it is present, 637 Since 0.4.7.2-alpha, when it is present, 639 638 the authorities will automatically vote against 640 639 flags that would make the router 641 usable in other positions. 642 (Since 0.4.7.2-alpha.) 640 usable in Guard, HSDir, Exit, and V2Dir. Additionally, 641 since Tor 0.4.8.15, clients and services will also avoid 642 usage of MiddleOnly nodes in IP and RP positions. - Comment on lines 635 to +642
Query on this for arti#1911 --
If a client sees MiddleOnly, is the client now responsible for avoiding any use of the relay as a Guard or Exit, or can the client assume that the authorities have not voted for it in those roles?
As per the text here, authorities will automatically vote against flags that would make the router usable in Guard, HSDir, Exit, and V2Dir.
The client can assume that the authorities will have voted according to the spec.
Additionally, clients should avoid use of MiddleOnly nodes in the IP and RP positions.
(I'm not opposed to adding specific dirauth flags for IP and RP use, such that MiddleOnly then also removes those. But in order to address this security gap quickly, we went with client-enforcement first.)