i2p friendly tahoe create-node/create-client #2838

Closed
opened 2016-10-11 16:20:26 +00:00 by dawuud · 4 comments
dawuud commented 2016-10-11 16:20:26 +00:00
Owner

add support for i2p specific arguments to automate the creation of tahoe clients and nodes.

add support for i2p specific arguments to automate the creation of tahoe clients and nodes.
tahoe-lafs added the
unknown
normal
defect
1.11.0
labels 2016-10-11 16:20:26 +00:00
tahoe-lafs added this to the undecided milestone 2016-10-11 16:20:26 +00:00

See #2490 for all discussion on this, and the corresponding implementation for Tor.

See #2490 for all discussion on this, and the corresponding implementation for Tor.

This should be relatively simple to implement to first-order, because txi2p already includes server endpoints. We just need an I2P provider to wrap the server endpoint, and integrate it into the appropriate locations / config options.

A full implementation with starting and stopping of I2P nodes would block on having support for this in txi2p, which I don't have time to implement right now (but could do so in future, or accept PRs that do). So for now I propose that the implementation support those same flags for I2P, but error if they are configured to inform the user that they are not yet implemented.

This should be relatively simple to implement to first-order, because txi2p already includes server endpoints. We just need an I2P provider to wrap the server endpoint, and integrate it into the appropriate locations / config options. A full implementation with starting and stopping of I2P nodes would block on having support for this in txi2p, which I don't have time to implement right now (but could do so in future, or accept PRs that do). So for now I propose that the implementation support those same flags for I2P, but error if they are configured to inform the user that they are not yet implemented.
warner modified the milestone from undecided to 1.12.0 2016-10-18 16:24:57 +00:00
str4d was assigned by warner 2016-10-18 16:25:17 +00:00

Take a look at src/allmydata/util/tor_provider.py

Take a look at src/allmydata/util/tor_provider.py
str4d <str4d@mail.i2p> commented 2016-10-24 02:03:32 +00:00
Author
Owner

In 6071c2b/trunk:

Implement i2p_provider and --listen=i2p

Closes ticket:2838
In [6071c2b/trunk](/tahoe-lafs/trac-2024-07-25/commit/6071c2b6f82cab20a30c6e2d285bad83514d7bb9): ``` Implement i2p_provider and --listen=i2p Closes ticket:2838 ```
tahoe-lafs added the
fixed
label 2016-10-24 02:03:32 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
3 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#2838
No description provided.