Skip to content

Commit 542927e

Browse files
committed
add ip privacy section
1 parent eb7bbbd commit 542927e

File tree

1 file changed

+45
-0
lines changed

1 file changed

+45
-0
lines changed

deployment/security-privacy.mdx

Lines changed: 45 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -36,3 +36,48 @@ you use [dedicated infrastructure](/deployment/dedicated-infrastructure) for pro
3636
We monitor the public relays for abuse and malicious activity. If we detect
3737
abuse, we reserve the right to block offending IP addresses or users from
3838
accessing the public relays.
39+
40+
## IP Privacy and Peer-to-Peer Connections
41+
42+
Peer-to-peer networking with direct connections and hole-punching is fundamentally
43+
incompatible with IP address privacy. When two endpoints establish a direct
44+
connection, they necessarily exchange and expose their IP addresses to each other.
45+
This is a core requirement of how direct peer-to-peer connections work.
46+
47+
However, peer-to-peer in the sense of **end-to-end encryption** is fully compatible
48+
with IP privacy, as encryption protects the content of your communications regardless
49+
of network topology.
50+
51+
If you need both end-to-end encryption and IP address privacy, you have several options:
52+
53+
### Option 1: Use Tor or Similar Onion Routing
54+
55+
Services like Tor provide onion routing, which encrypts packet metadata for each
56+
relay in the route. This offers strong IP privacy guarantees through multi-hop
57+
routing with layered encryption.
58+
59+
### Option 2: Relay-Only Mode (Upcoming)
60+
61+
Upcoming releases of iroh will support disabling hole-punching to send all traffic
62+
exclusively through relays. This provides IP privacy with some important caveats:
63+
64+
- **Single-hop routing**: Traffic passes through one relay, not multiple hops
65+
- **Trust required**: The relay operator can technically see which endpoints are
66+
communicating and their IP addresses
67+
- **Data remains encrypted**: The relay cannot read the actual content due to
68+
end-to-end encryption
69+
70+
This mode is suitable when you trust your relay infrastructure but still want to
71+
avoid direct IP exposure between endpoints.
72+
73+
### Future: Multi-Hop Relay Routing
74+
75+
We've explored the possibility of adding multi-hop relay routing to iroh. While
76+
technically feasible, this feature is not currently on the near-term roadmap.
77+
78+
It's important to note that even with multi-hop relay routing, this would not be
79+
equivalent to onion routing. True onion routing requires encrypting packet metadata
80+
for each relay in the route, which would require significant protocol changes.
81+
82+
If these features are interesting to you, please [contact us](https://n0.computer/)
83+
to discuss your specific requirements.

0 commit comments

Comments
 (0)