[tahoe-dev] Fwd: [Foolscap] #151: Accept I2P destinations

[duck]

Since it is needed for Tahoe-LAFS on I2P:

---------- Forwarded message ----------
From: Foolscap <trac at foolscap.lothar.com>
Date: Wed, Jan 12, 2011 at 9:47 PM
Subject: Re: [Foolscap] #151: Accept I2P destinations
To:


#151: Accept I2P destinations
--------------------------+-------------------------------------------------
 Reporter:  duck         |       Owner:  duck
     Type:  enhancement  |      Status:  new
 Priority:  minor        |   Milestone:  undecided
 Component:  unknown      |     Version:  0.5.0
Resolution:               |    Keywords:  i2p transport
--------------------------+-------------------------------------------------
Comment (by duck):

 Brian's suggestion to use the name: prefix (i2p:) has been taken.
 Detection based on the ".b32.i2p" postfix has been deprecated; it can be
 dropped after the entire I2P Tahoe-LAFS network has upgraded to Tahoe-Lafs
 1.8.1 and Foolscap 0.6.0.

 I disagree with deciding to use link the http proxy usage to detecting the
 address being for i2p. This would allow for de-anonymizing attacks.

 Unit tests have been written as well.

--
Ticket URL: <http://foolscap.lothar.com/trac/ticket/151#comment:7>
Foolscap <http://foolscap.lothar.com>
secure remote object communication for Twisted