{"id":6156,"date":"2026-09-04T23:10:10","date_gmt":"2026-09-04T14:10:10","guid":{"rendered":"https:\/\/eternalsphere.net\/echoes\/?p=6156"},"modified":"2026-09-12T14:03:04","modified_gmt":"2026-09-12T05:03:04","slug":"lnxeb9xs7ysbbxn","status":"publish","type":"post","link":"https:\/\/blog.eternalsphere.net\/index.php\/2026\/09\/04\/lnxeb9xs7ysbbxn\/","title":{"rendered":"Bridge, Guard, Middle, and Exit: Understanding the Different Roles Inside the Tor Network"},"content":{"rendered":"\n

When people first learn about Tor, terms such as Bridge<\/strong>, Guard relay<\/strong>, Middle relay<\/strong>, and Exit relay<\/strong> can sound like different \u201clevels\u201d of the same system.<\/p>\n\n\n\n

That interpretation is only partly correct.<\/p>\n\n\n\n

These terms actually describe different roles within Tor’s network architecture<\/strong>. Some roles are closely related, while others exist for completely different purposes.<\/p>\n\n\n\n

Understanding the distinction makes the Tor network much easier to visualize.<\/p>\n\n\n\n

\n\n\n\n

Tor Is a Network of Relays<\/h2>\n\n\n\n

Tor does not normally connect a user directly to a website.<\/p>\n\n\n\n

Instead, traffic passes through several independently operated Tor relays.<\/p>\n\n\n\n

A simplified Tor circuit looks like this:<\/p>\n\n\n\n

User\n  \u2502\n  \u25bc\nGuard Relay\n  \u2502\n  \u25bc\nMiddle Relay\n  \u2502\n  \u25bc\nExit Relay\n  \u2502\n  \u25bc\nInternet Destination\n<\/code><\/pre>\n\n\n\n
Each relay knows only part of the communication path.<\/p>\n\n\n\n
This separation is fundamental to Tor’s privacy model.<\/p>\n\n\n\n
The Guard knows where the connection came from, but normally does not know its final destination.<\/p>\n\n\n\n
The Exit knows the final destination, but normally does not know the original user’s IP address.<\/p>\n\n\n\n
The Middle connects the two without normally knowing either endpoint.<\/p>\n\n\n\n
This is why Tor is often described as using layered routing<\/strong>.<\/p>\n\n\n\n
\n\n\n\n
1. What Is a Guard Relay?<\/h1>\n\n\n\n
A Guard relay<\/strong>, sometimes called an Entry Guard<\/strong>, is the first public Tor relay in a user’s circuit.<\/p>\n\n\n\n
The basic path is:<\/p>\n\n\n\n
User\n  \u2502\n  \u25bc\nGuard\n  \u2502\n  \u25bc\nMiddle\n  \u2502\n  \u25bc\nExit\n<\/code><\/pre>\n\n\n\n
The Guard is therefore the Tor relay closest to the user.<\/p>\n\n\n\n
Because the user connects directly to it, the Guard can normally observe the user’s source IP address.<\/p>\n\n\n\n
However, it cannot normally see the final website being accessed.<\/p>\n\n\n\n
Conceptually, its knowledge looks like this:<\/p>\n\n\n\n
Guard knows:\n\nUser IP\n   \u2502\n   \u25bc\nGuard\n   \u2502\n   \u25bc\nanother Tor relay\n<\/code><\/pre>\n\n\n\n
It does not see:<\/p>\n\n\n\n
User IP\n+\nfinal website\n<\/code><\/pre>\n\n\n\n
as one complete path.<\/p>\n\n\n\n
\n\n\n\n
Why Does Tor Use Guards?<\/h2>\n\n\n\n
One might imagine that choosing a completely random first relay every time would provide better anonymity.<\/p>\n\n\n\n
In practice, it creates another problem.<\/p>\n\n\n\n
Suppose a small percentage of Tor relays are controlled by an attacker.<\/p>\n\n\n\n
If users continually select random entry relays, eventually they may connect through a malicious one.<\/p>\n\n\n\n
The more circuits they create, the more chances an attacker gets.<\/p>\n\n\n\n
Tor therefore prefers to keep a relatively small set of trusted entry relays for longer periods.<\/p>\n\n\n\n
These are called Guards<\/strong>.<\/p>\n\n\n\n
The basic idea is:<\/p>\n\n\n\n
Constantly changing entry relay\n        \u2193\nmany opportunities to eventually encounter a malicious relay\n\nStable Guard selection\n        \u2193\nfewer entry relays exposed to the user\n<\/code><\/pre>\n\n\n\n
This reduces certain traffic-correlation risks.<\/p>\n\n\n\n
\n\n\n\n
2. What Is a Middle Relay?<\/h1>\n\n\n\n
A Middle relay<\/strong> carries traffic between other Tor relays.<\/p>\n\n\n\n
In a typical circuit:<\/p>\n\n\n\n
User\n  \u2502\nGuard\n  \u2502\nMiddle\n  \u2502\nExit\n  \u2502\nInternet\n<\/code><\/pre>\n\n\n\n
the Middle does not directly communicate with either the user or the destination website.<\/p>\n\n\n\n
Instead, it sees something more like:<\/p>\n\n\n\n
Tor Relay A\n     \u2502\n     \u25bc\n Middle\n     \u2502\n     \u25bc\nTor Relay B\n<\/code><\/pre>\n\n\n\n
From the Middle relay’s perspective, both sides are usually simply other Tor nodes.<\/p>\n\n\n\n
This makes the Middle role particularly interesting from an operational perspective.<\/p>\n\n\n\n
A Middle relay does not normally generate traffic directly toward websites, email servers, or other Internet services.<\/p>\n\n\n\n
As a result, it generally produces far fewer abuse complaints than an Exit relay.<\/p>\n\n\n\n
For volunteer operators, this is one reason a non-exit relay is often the most straightforward way to contribute bandwidth to Tor.<\/p>\n\n\n\n
\n\n\n\n
3. Is a Guard a \u201cHigher-Level Middle Relay\u201d?<\/h1>\n\n\n\n
In a limited sense, there is a relationship.<\/p>\n\n\n\n
But calling Guard and Middle different \u201clevels\u201d is misleading.<\/p>\n\n\n\n
A new public non-exit relay usually begins life primarily as a general relay and may initially be used in the Middle position.<\/p>\n\n\n\n
If it remains:<\/p>\n\n\n\n
    \n
  • stable,<\/li>\n\n\n\n
  • reachable,<\/li>\n\n\n\n
  • sufficiently fast,<\/li>\n\n\n\n
  • consistently online,<\/li>\n<\/ul>\n\n\n\n
    the Tor directory authorities may eventually mark it as suitable for Guard usage.<\/p>\n\n\n\n
    Conceptually:<\/p>\n\n\n\n
    New public relay\n       \u2502\n       \u25bc\nPrimarily usable as Middle\n       \u2502\n       \u25bc\nLong-term stability\nGood uptime\nAdequate bandwidth\n       \u2502\n       \u25bc\nMay receive Guard eligibility\n<\/code><\/pre>\n\n\n\n
    The operator does not simply declare:<\/p>\n\n\n\n
    \"This server is now a Guard.\"\n<\/code><\/pre>\n\n\n\n
    The Tor network evaluates relay characteristics and assigns flags accordingly.<\/p>\n\n\n\n
    Therefore:<\/p>\n\n\n\n
    Middle and Guard are roles within the public Tor relay system.<\/strong><\/p>\n\n\n\n
    A relay may become eligible for the Guard role after demonstrating sufficient reliability.<\/p>\n\n\n\n
    \n\n\n\n
    4. What Is an Exit Relay?<\/h1>\n\n\n\n
    The Exit relay<\/strong> is the final Tor relay before traffic reaches the ordinary Internet.<\/p>\n\n\n\n
    Its position is:<\/p>\n\n\n\n
    User\n  \u2502\nGuard\n  \u2502\nMiddle\n  \u2502\nExit\n  \u2502\n  \u25bc\nWebsite\n<\/code><\/pre>\n\n\n\n
    From the destination website’s perspective, the connection appears to originate from the Exit relay.<\/p>\n\n\n\n
    For example:<\/p>\n\n\n\n
    User real IP:\n203.0.113.10\n\nExit IP:\n198.51.100.25\n\nWebsite sees:\n198.51.100.25\n<\/code><\/pre>\n\n\n\n
    The website does not normally see the user’s real IP.<\/p>\n\n\n\n
    This makes the Exit one of the most important components of Tor\u2014but also the most operationally sensitive.<\/p>\n\n\n\n
    \n\n\n\n
    Why Exit Relays Receive Abuse Complaints<\/h2>\n\n\n\n
    Consider a Tor user connecting to an ordinary website:<\/p>\n\n\n\n
    User\n \u2193\nGuard\n \u2193\nMiddle\n \u2193\nExit\n \u2193\nWebsite\n<\/code><\/pre>\n\n\n\n
    The website sees only:<\/p>\n\n\n\n
    Exit \u2192 Website\n<\/code><\/pre>\n\n\n\n
    If someone abuses the service, the resulting logs may therefore contain the Exit relay’s IP address.<\/p>\n\n\n\n
    Consequently, complaints may initially be sent to:<\/p>\n\n\n\n
      \n
    • the Exit operator,<\/li>\n\n\n\n
    • its hosting provider,<\/li>\n\n\n\n
    • its ISP,<\/li>\n\n\n\n
    • or the organization owning the IP range.<\/li>\n<\/ul>\n\n\n\n
      This does not mean the Exit operator performed the activity.<\/p>\n\n\n\n
      It simply means that the Exit was the last visible network hop.<\/p>\n\n\n\n
      That distinction is one of the most important concepts in understanding Tor infrastructure.<\/p>\n\n\n\n
      \n\n\n\n
      5. What Is a Bridge?<\/h1>\n\n\n\n
      A Bridge<\/strong> is fundamentally different from Guard, Middle, and Exit.<\/p>\n\n\n\n
      Its primary purpose is not to occupy a particular numbered position in an ordinary Tor circuit.<\/p>\n\n\n\n
      Instead, a Bridge exists to help users connect to Tor when normal Tor relays are blocked.<\/p>\n\n\n\n
      \n\n\n\n
      The Problem With Public Relays<\/h2>\n\n\n\n
      Normal Tor relays are publicly listed.<\/p>\n\n\n\n
      Tor clients need to discover them somehow, so information about public relays is distributed through Tor’s directory system.<\/p>\n\n\n\n
      That means a censor can also obtain those addresses.<\/p>\n\n\n\n
      A simple blocking strategy could therefore be:<\/p>\n\n\n\n
      Download Tor relay list\n       \u2502\n       \u25bc\nCollect public relay IP addresses\n       \u2502\n       \u25bc\nBlock all of them\n<\/code><\/pre>\n\n\n\n
      In such an environment, ordinary Tor connections may stop working.<\/p>\n\n\n\n
      \n\n\n\n
      6. Bridges Exist to Make Blocking Harder<\/h1>\n\n\n\n
      A Bridge is an entry relay whose address is not published in the normal public relay directory<\/strong>.<\/p>\n\n\n\n
      Instead of:<\/p>\n\n\n\n
      Public Tor relay\n      \u2502\n      \u25bc\nIP visible in public relay directory\n<\/code><\/pre>\n\n\n\n
      a Bridge works more like:<\/p>\n\n\n\n
      Bridge\n  \u2502\n  \u25bc\naddress distributed through restricted mechanisms\n<\/code><\/pre>\n\n\n\n
      This makes mass blocking more difficult.<\/p>\n\n\n\n
      Bridges are therefore mainly a censorship-resistance mechanism<\/strong>.<\/p>\n\n\n\n
      They are especially useful in networks where direct connections to known Tor infrastructure are filtered.<\/p>\n\n\n\n
      \n\n\n\n
      7. Bridge and Guard May Look Similar, But Their Purpose Is Different<\/h1>\n\n\n\n
      Both Bridges and Guards can appear close to the beginning of a Tor connection.<\/p>\n\n\n\n
      For that reason, they are easy to confuse.<\/p>\n\n\n\n
      An ordinary Tor connection might look like:<\/p>\n\n\n\n
      User\n  \u2502\n  \u25bc\nGuard\n  \u2502\n  \u25bc\nMiddle\n  \u2502\n  \u25bc\nExit\n<\/code><\/pre>\n\n\n\n
      A connection using a Bridge might look approximately like:<\/p>\n\n\n\n
      User\n  \u2502\n  \u25bc\nBridge\n  \u2502\n  \u25bc\nTor Network\n  \u2502\n  \u25bc\nExit\n<\/code><\/pre>\n\n\n\n
      But their purposes are different.<\/p>\n\n\n\n
      A Guard<\/strong> exists mainly to provide a stable and secure first hop within the normal public Tor network.<\/p>\n\n\n\n
      A Bridge<\/strong> exists mainly so that users can reach Tor even when public relay addresses are blocked.<\/p>\n\n\n\n
      This distinction is crucial.<\/p>\n\n\n\n
      \n\n\n\n
      8. So Are Bridge, Guard, and Middle Different Levels?<\/h1>\n\n\n\n
      No.<\/p>\n\n\n\n
      A better classification is:<\/p>\n\n\n\n
      Tor Infrastructure\n\u2502\n\u251c\u2500\u2500 Public Relays\n\u2502   \u2502\n\u2502   \u251c\u2500\u2500 Guard\n\u2502   \u2502   \u2514\u2500\u2500 entry role\n\u2502   \u2502\n\u2502   \u251c\u2500\u2500 Middle\n\u2502   \u2502   \u2514\u2500\u2500 internal forwarding role\n\u2502   \u2502\n\u2502   \u2514\u2500\u2500 Exit\n\u2502       \u2514\u2500\u2500 connection to ordinary Internet\n\u2502\n\u2514\u2500\u2500 Bridges\n    \u2514\u2500\u2500 non-public entry infrastructure\n<\/code><\/pre>\n\n\n\n
      This model is much more accurate than imagining:<\/p>\n\n\n\n
      Bridge\n  \u2193\nMiddle\n  \u2193\nGuard\n  \u2193\nExit\n<\/code><\/pre>\n\n\n\n
      as if they were ranks or upgrade levels.<\/p>\n\n\n\n
      They are not.<\/p>\n\n\n\n
      \n\n\n\n
      9. One Machine Can Have Different Roles Over Time<\/h1>\n\n\n\n
      Another source of confusion is that Tor relay roles are not necessarily permanently fixed.<\/p>\n\n\n\n
      A public non-exit relay might initially function mostly as a Middle.<\/p>\n\n\n\n
      After demonstrating sufficient stability and bandwidth, it may later qualify as a Guard.<\/p>\n\n\n\n
      Therefore:<\/p>\n\n\n\n
      Physical server\n      \u2502\n      \u25bc\nTor relay identity\n      \u2502\n      \u251c\u2500\u2500 initially used as Middle\n      \u2502\n      \u2514\u2500\u2500 later possibly eligible as Guard\n<\/code><\/pre>\n\n\n\n
      The machine itself has not necessarily changed.<\/p>\n\n\n\n
      Its role within the Tor network has.<\/p>\n\n\n\n
      This is why Guard and Middle should often be thought of as selection roles assigned to public relays<\/strong>, rather than entirely different classes of hardware.<\/p>\n\n\n\n
      \n\n\n\n
      10. Exit Is Different Again<\/h1>\n\n\n\n
      Exit capability is more deliberate.<\/p>\n\n\n\n
      A Tor operator must explicitly permit certain outbound destinations and ports through an Exit Policy<\/strong>.<\/p>\n\n\n\n
      A non-exit relay effectively says:<\/p>\n\n\n\n
      Relay Tor traffic\nbut do not send it onto the ordinary Internet\n<\/code><\/pre>\n\n\n\n
      An Exit relay says:<\/p>\n\n\n\n
      Relay Tor traffic\nand allow selected traffic to leave Tor\n<\/code><\/pre>\n\n\n\n
      This distinction has major operational consequences.<\/p>\n\n\n\n
      A Middle or Guard usually communicates primarily with other Tor relays.<\/p>\n\n\n\n
      An Exit communicates directly with arbitrary Internet services.<\/p>\n\n\n\n
      That is why Exit operation generally involves significantly more administrative, legal, and abuse-management considerations.<\/p>\n\n\n\n
      \n\n\n\n
      11. What Does Each Relay Know?<\/h1>\n\n\n\n
      A simplified view helps illustrate Tor’s compartmentalization.<\/p>\n\n\n\n
      Guard<\/h2>\n\n\n\n
      The Guard can generally know:<\/p>\n\n\n\n
      User IP\n+\nnext Tor relay\n<\/code><\/pre>\n\n\n\n
      but not the final Internet destination.<\/p>\n\n\n\n
      \n\n\n\n
      Middle<\/h2>\n\n\n\n
      The Middle generally knows:<\/p>\n\n\n\n
      previous Tor relay\n+\nnext Tor relay\n<\/code><\/pre>\n\n\n\n
      but not the original user and final destination together.<\/p>\n\n\n\n
      \n\n\n\n
      Exit<\/h2>\n\n\n\n
      The Exit generally knows:<\/p>\n\n\n\n
      previous Tor relay\n+\ndestination server\n<\/code><\/pre>\n\n\n\n
      but not the original user’s IP address.<\/p>\n\n\n\n
      \n\n\n\n
      Destination Website<\/h2>\n\n\n\n
      The destination generally knows:<\/p>\n\n\n\n
      Exit IP\n<\/code><\/pre>\n\n\n\n
      but not the original user’s network address.<\/p>\n\n\n\n
      That separation is central to onion routing.<\/p>\n\n\n\n
      \n\n\n\n
      12. Where Does a Bridge Fit Into This Privacy Model?<\/h1>\n\n\n\n
      A Bridge does not replace the entire Tor circuit.<\/p>\n\n\n\n
      It primarily changes how the user enters<\/strong> the Tor network.<\/p>\n\n\n\n
      Conceptually:<\/p>\n\n\n\n
      Normal connection:\n\nUser\n \u2193\nPublic Guard\n \u2193\nTor Network\n\n\nBridge connection:\n\nUser\n \u2193\nNon-public Bridge\n \u2193\nTor Network\n<\/code><\/pre>\n\n\n\n
      The remainder of Tor’s layered routing architecture still applies.<\/p>\n\n\n\n
      The key advantage is that the user’s ISP or local network cannot simply compare the destination IP against the ordinary public Tor relay list.<\/p>\n\n\n\n
      Modern Bridge systems can also use pluggable transports designed to make Tor traffic harder to identify through traffic inspection.<\/p>\n\n\n\n
      \n\n\n\n
      13. Why Bridges Are Not Completely Secret<\/h1>\n\n\n\n
      \u201cNot publicly listed\u201d does not mean \u201cimpossible to discover.\u201d<\/p>\n\n\n\n
      If Bridge addresses were completely inaccessible, legitimate users would not be able to obtain them either.<\/p>\n\n\n\n
      Tor therefore distributes Bridge information through controlled channels.<\/p>\n\n\n\n
      This creates a continual contest:<\/p>\n\n\n\n
      Tor:\nmake bridges available to real users\nwithout publishing everything openly\n\nCensors:\nattempt to discover and block bridges\n<\/code><\/pre>\n\n\n\n
      This is why Bridge architecture is a specialized area of censorship resistance.<\/p>\n\n\n\n
      \n\n\n\n
      14. Relay Role vs. Physical Server<\/h1>\n\n\n\n
      Another useful distinction is between a relay identity<\/strong> and a physical machine<\/strong>.<\/p>\n\n\n\n
      When statistics say that a country has a certain number of Tor relays, that does not necessarily mean the same number of separate servers.<\/p>\n\n\n\n
      For example:<\/p>\n\n\n\n
      One physical server\n\u2502\n\u251c\u2500\u2500 Relay identity A\n\u251c\u2500\u2500 Relay identity B\n\u2514\u2500\u2500 Relay identity C\n<\/code><\/pre>\n\n\n\n
      Multiple Tor relay instances can sometimes exist on one host or public IP.<\/p>\n\n\n\n
      Conversely, one operator may run relays across many machines, networks, or countries.<\/p>\n\n\n\n
      Therefore Tor statistics should be interpreted carefully.<\/p>\n\n\n\n
      \n\n\n\n
      15. A Practical Operator’s Perspective<\/h1>\n\n\n\n
      From the viewpoint of someone contributing infrastructure to Tor, the roles also differ significantly.<\/p>\n\n\n\n
      Bridge<\/h3>\n\n\n\n
      Primary purpose:<\/p>\n\n\n\n
      Help users reach Tor when public relays are blocked.<\/strong><\/p>\n\n\n\n
      Advantages:<\/p>\n\n\n\n
        \n
      • not listed in the normal public relay directory,<\/li>\n\n\n\n
      • useful against censorship,<\/li>\n\n\n\n
      • generally low abuse exposure.<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n
        Middle Relay<\/h3>\n\n\n\n
        Primary purpose:<\/p>\n\n\n\n
        Provide bandwidth inside the Tor network.<\/strong><\/p>\n\n\n\n
        Advantages:<\/p>\n\n\n\n
          \n
        • relatively simple operation,<\/li>\n\n\n\n
        • little direct interaction with destination websites,<\/li>\n\n\n\n
        • low abuse complaint exposure,<\/li>\n\n\n\n
        • useful contribution even without Exit operation.<\/li>\n<\/ul>\n\n\n\n
          \n\n\n\n
          Guard Relay<\/h3>\n\n\n\n
          Primary purpose:<\/p>\n\n\n\n
          Provide trusted, stable entry capacity.<\/strong><\/p>\n\n\n\n
          Characteristics:<\/p>\n\n\n\n
            \n
          • publicly listed,<\/li>\n\n\n\n
          • requires strong uptime and reliability,<\/li>\n\n\n\n
          • usually becomes Guard-eligible based on network evaluation.<\/li>\n<\/ul>\n\n\n\n
            \n\n\n\n
            Exit Relay<\/h3>\n\n\n\n
            Primary purpose:<\/p>\n\n\n\n
            Connect Tor users to the ordinary Internet.<\/strong><\/p>\n\n\n\n
            Characteristics:<\/p>\n\n\n\n
              \n
            • extremely important to the network,<\/li>\n\n\n\n
            • destination services see its IP,<\/li>\n\n\n\n
            • highest abuse-management burden,<\/li>\n\n\n\n
            • requires careful operational planning.<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n
              16. The Simplest Mental Model<\/h1>\n\n\n\n
              The entire distinction can be reduced to four sentences:<\/p>\n\n\n\n
              Bridge:<\/strong>
              \u201cHelp users get into Tor when Tor is blocked.\u201d<\/p>\n\n\n\n
              Guard:<\/strong>
              \u201cBe the stable first public relay in a Tor circuit.\u201d<\/p>\n\n\n\n
              Middle:<\/strong>
              \u201cMove encrypted traffic between Tor relays.\u201d<\/p>\n\n\n\n
              Exit:<\/strong>
              \u201cTake Tor traffic out to the normal Internet.\u201d<\/p>\n\n\n\n
              Or visually:<\/p>\n\n\n\n
                                       \u250c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2510\n                         \u2502 Public Guard  \u2502\n                         \u2514\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u252c\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2518\n                                 \u2502\nUser \u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2524\n                                 \u25bc\n                          Middle Relay\n                                 \u2502\n                                 \u25bc\n                           Exit Relay\n                                 \u2502\n                                 \u25bc\n                             Internet\n\n\nAlternative censored-network entry:\n\nUser\n \u2502\n \u25bc\nBridge\n \u2502\n \u25bc\nTor Network\n \u2502\n \u25bc\nExit\n \u2502\n \u25bc\nInternet\n<\/code><\/pre>\n\n\n\n
              \n\n\n\n
              Conclusion<\/h1>\n\n\n\n
              Bridge, Guard, Middle, and Exit are not four ranks of Tor relay.<\/p>\n\n\n\n
              They represent different functions.<\/p>\n\n\n\n
              Guard, Middle, and Exit describe positions or capabilities inside the public Tor relay architecture.<\/strong><\/p>\n\n\n\n
              Bridge describes a special non-public entry mechanism designed primarily to resist censorship.<\/strong><\/p>\n\n\n\n
              Among public relays, a new non-exit relay may initially function mainly as a Middle and later become Guard-eligible after demonstrating sufficient stability.<\/p>\n\n\n\n
              Exit operation is different because it allows traffic to leave Tor and reach the ordinary Internet directly.<\/p>\n\n\n\n
              The resulting architecture can therefore be summarized as:<\/p>\n\n\n\n
              Public Tor Network\n\u2502\n\u251c\u2500\u2500 Guard\n\u251c\u2500\u2500 Middle\n\u2514\u2500\u2500 Exit\n\nCensorship-resistant entry\n\u2502\n\u2514\u2500\u2500 Bridge\n<\/code><\/pre>\n\n\n\n
              Once this distinction is understood, much of Tor’s architecture becomes easier to reason about.<\/p>\n\n\n\n
              Tor is not built around a hierarchy of \u201chigher\u201d and \u201clower\u201d relays.<\/p>\n\n\n\n
              It is built around specialization, separation of knowledge, and distribution of trust<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"
              When people first learn about Tor, terms such as Bridge, Guard relay, Middle relay, and Exit relay can sound like different \u201clevels\u201d of the same system. That interpretation is only partly correct. These terms actually describe different roles within Tor’s network architecture. Some roles are closely related, while others exist …<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[120],"tags":[245],"class_list":["post-6156","post","type-post","status-publish","format-standard","hentry","category-1s3b6h7r2zay02x","tag-tor"],"_links":{"self":[{"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/posts\/6156","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/comments?post=6156"}],"version-history":[{"count":1,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/posts\/6156\/revisions"}],"predecessor-version":[{"id":6157,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/posts\/6156\/revisions\/6157"}],"wp:attachment":[{"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/media?parent=6156"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/categories?post=6156"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/tags?post=6156"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}