Opened 17 months ago

Last modified 14 months ago

#30623 new task

may prop 110 + 292 making hs discovery easier?

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: unspecified
Severity: Normal Keywords: needs-review, 042-deferred-20190918
Cc: mikeperry Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I have read both:

If an intermediate server receives more than K relay_early cells,
  • proposals/292-mesh-vanguards.txt
    Additionally, to avoid linkability, we insert an extra middle node
      after the third layer guard for client side intro and hsdir circuits,
      and service-side rendezvous circuits. This means that the set of
      paths for Client (C) and Service (S) side look like this:

and found that with the extra 4th random middle node added by vanguards circlen, a onion Service using vanguards does not blend in with other services or clients. As each intermediate guards server should passively be able to Monitor by listening receives more than usual relay_early cells with (plus ) extra vanguard relay_early cell and find out node's position in the circuit is guard for that the connecting or is a hidden Service with using vanguards addon enabled easily?
please check..

Child Tickets

Change History (3)

comment:1 Changed 17 months ago by nickm

Cc: mikeperry added
Milestone: Tor: 0.4.2.x-final

Mike, can you have a look here?

comment:2 Changed 17 months ago by cypherpunks

In other words. prop292 makes you stand out?

If a relay observers the one more relay_early cells on a circuit, it can guess that it is in a (van)guard position of serving a hiddenservice with vanguard enabled?

When this can be confirmed, it is not very in aim of the vanguards addon at all. Because not many actually shoul'd be using it at all. But ones who need strong anonymity. If this is the case, it will reduce onion services anonymity.

comment:3 Changed 14 months ago by nickm

Keywords: 042-deferred-20190918 added
Milestone: Tor: 0.4.2.x-finalTor: unspecified

Deferring various tickets from 0.4.2 to Unspecified.

Note: See TracTickets for help on using tickets.