Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #30623

Closed (moved)
(moved)
Open
Created May 26, 2019 by cypherpunks@cypherpunks

may prop 110 + 292 making hs discovery easier?

I have read both:

  • proposals/110-avoid-infinite-circuits.txt
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..

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking