In privacy mode, only explicitly allowed TCP/UDP connections should happen #4031

Open
opened 2023-05-24 14:25:48 +00:00 by itamarst · 0 comments
itamarst commented 2023-05-24 14:25:48 +00:00
Owner

If Tahoe is configured in private IP mode (Tor, I2P, or some future mode) there is the possibility of random parts not respecting this. E.g. HTTP storage protocol had this issue until #4029.

One solution is to have the core networking APIs, i.e. the reactor, setup such that connections are only allowed to the entry point to Tor/I2P, and all other connections fail. If e.g. the introducer was switched to a HTTP protocol, and it had the same flaw as the HTTP storage protocol of not respecting Tor, this enforcement would cause it to fail to work, rather than silently violating privacy guarantees.

If Tahoe is configured in private IP mode (Tor, I2P, or some future mode) there is the possibility of random parts not respecting this. E.g. HTTP storage protocol had this issue until #4029. One solution is to have the core networking APIs, i.e. the reactor, setup such that connections are only allowed to the entry point to Tor/I2P, and all other connections fail. If e.g. the introducer was switched to a HTTP protocol, and it had the same flaw as the HTTP storage protocol of not respecting Tor, this enforcement would cause it to fail to work, rather than silently violating privacy guarantees.
tahoe-lafs added the
unknown
normal
defect
n/a
labels 2023-05-24 14:25:48 +00:00
tahoe-lafs added this to the HTTP Storage Protocol v2 milestone 2023-05-24 14:25:48 +00:00
Sign in to join this conversation.
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#4031
No description provided.