[tor-dev] Onioncat and Prop224

[str4d]

On 27/04/16 22:31, grarpamp wrote:
> On 4/25/16, Tim Wilson-Brown - teor <teor2345 at gmail.com> wrote:
>>
>>> On 22 Apr 2016, at 17:03, grarpamp <grarpamp at gmail.com> wrote:
>>>
>>> FYI: The onioncat folks are interested in collaborating
>>> with tor folks regarding prop224.
>>>
>>> https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt
>>
>> I'm interested in what kind of collaboration onioncat would like to do on
>> prop224, next-generation hidden services.
>> It would be great to work this out in the next few weeks, as we're coding
>> parts of the proposal right now.
> 
> Yep :) And I know Bernhard was hoping to get in touch with Roger
> on this before long.
> 
> Basically, prop224 HS being wider than 80 bits will break onioncat's
> current HS onion <---> IPv6 addressing mechanism.
> 
> They're looking at various backward compatibility options, as well
> as possibly making side use of the HSDir DHT, or even integrating
> more directly with the tor client.
> 

Just FYI, I recently migrated all of I2P's spec proposals to the
website, and came across a seven-year-old proposal that Bernhard wrote
about improving I2P support in GarliCat:

https://geti2p.net/spec/proposals/105-garlicat-name-translation

I don't know how well it has aged, but given that Tor is now facing the
same issues that I2P has, perhaps it can be of some use if resurrected
from the dead :)

> 
>> But the tor-onions mailing list is to discuss the technical details running
>> onion services.
> 
> Readers of tor-onions / newbies may have been unfamiliar with
> onioncat. It's a way to get non-TCP between TorHS onions, thus in
> the thread "Hidden datagram service".
> 
> I think there are a nontrivial number of users interested in, and
> using, non-strictly-TCP transport over an IPv6 tunnel interface.
> For example, look at users of CJDNS...
> 
> For which we should try to continue a way, in v2, to do that over
> anonymous overlay network Tor / I2P.
> 

There is already some work on doing this in I2P:

https://github.com/majestrate/i2p-tools/tree/master/i2tun
https://github.com/majestrate/i2p-tools/tree/master/pyi2tun

I2P also natively supports non-TCP protocols if that helps (only
datagrams implemented thus far).

str4d

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20160430/a93ed9c1/attachment.sig>