Multiple introducers, through relay #1402

Closed
opened 2011-05-12 00:06:03 +00:00 by socrates · 3 comments
socrates commented 2011-05-12 00:06:03 +00:00
Owner

I decided to take a crack at the multiple introducers problem.
I've implemented a proof of concept relay, that connects to two, or more, introducer nodes and relays announcements between them.

This would be used to connect two, or more, separate grids, so that nodes connected to either introducer, would would be aware of nodes connected to other introducers.

Also, this demonstrates the fact that introducer nodes do not validate announcements at all, as the relay can easily modify the data it is relaying.

code attached:

I decided to take a crack at the multiple introducers problem. I've implemented a proof of concept relay, that connects to two, or more, introducer nodes and relays announcements between them. This would be used to connect two, or more, separate grids, so that nodes connected to either introducer, would would be aware of nodes connected to other introducers. Also, this demonstrates the fact that introducer nodes do not validate announcements at all, as the relay can easily modify the data it is relaying. code attached:
tahoe-lafs added the
code-network
major
enhancement
1.8.2
labels 2011-05-12 00:06:03 +00:00
tahoe-lafs added this to the undecided milestone 2011-05-12 00:06:03 +00:00
socrates commented 2011-05-12 00:07:15 +00:00
Author
Owner

Attachment relay.py (1685 bytes) added

relay.py - proof of concept for introducer relay

**Attachment** relay.py (1685 bytes) added relay.py - proof of concept for introducer relay
1.6 KiB

This seems redundant with #68. Merge the tickets?

This seems redundant with #68. Merge the tickets?

socrates: thanks for the patch! This ticket is redundant with #68, so I'm merging the two, but I'd also like to draw attention to this patch to readers of that ticket, so I'll post a comment there.

socrates: thanks for the patch! This ticket is redundant with #68, so I'm merging the two, but I'd also like to draw attention to this patch to readers of that ticket, so I'll post a comment there.
zooko added the
duplicate
label 2013-07-17 16:54:31 +00:00
zooko closed this issue 2013-07-17 16:54:31 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

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