Opened at 2016-10-11T16:20:26Z
Closed at 2016-10-24T02:03:32Z
#2838 closed defect (fixed)
i2p friendly tahoe create-node/create-client
Reported by: | dawuud | Owned by: | str4d |
---|---|---|---|
Priority: | normal | Milestone: | 1.12.0 |
Component: | unknown | Version: | 1.11.0 |
Keywords: | Cc: | ||
Launchpad Bug: | i2p anonymous |
Description
add support for i2p specific arguments to automate the creation of tahoe clients and nodes.
Change History (6)
comment:1 Changed at 2016-10-11T16:22:51Z by str4d
comment:2 Changed at 2016-10-11T16:30:08Z by str4d
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.
comment:3 Changed at 2016-10-18T16:24:57Z by warner
- Milestone changed from undecided to 1.12.0
comment:4 Changed at 2016-10-18T16:25:17Z by warner
- Owner set to str4d
comment:5 Changed at 2016-10-18T16:26:50Z by warner
Take a look at src/allmydata/util/tor_provider.py
comment:6 Changed at 2016-10-24T02:03:32Z by str4d <str4d@…>
- Resolution set to fixed
- Status changed from new to closed
In 6071c2b/trunk:
See #2490 for all discussion on this, and the corresponding implementation for Tor.