Opened 14 years ago

Last modified 7 years ago

#151 new enhancement

Accept I2P destinations — at Initial Version

Reported by: duck Owned by:
Priority: minor Milestone: undecided
Component: network Version: 0.5.0
Keywords: i2p transport review-needed i2p-collab Cc: Zooko, zooko@…, killyourtv@…

Description

To be able to use I2P with Foolscap (see #150 and ​Tahoe-LAFS #1007, I have extended decode_location_hint to accept I2P base32 destinations. Since I2P destinations can't have a port as part of the location, the current IPv4 regex doesn't work.

These I2P destinations look like this: 

3u2mqm3mvcyc27yliky3xnr4khpgfd4eeadhwwjneaqhj25a65ua.b32.i2p

They have the format: base32_encode(sha256_hash) + ".b32.i2p"

Change History (1)

Changed 14 years ago by duck

Attachment: 151_i2p_destinations.txt​ added

Recognize base32 I2P destinations.

Note: See TracTickets for help on using tickets.