From: grarpamp <grarpamp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Cc: phantom-protocol@googlegroups•com
Subject: Re: [Bitcoin-development] Tor hidden service support
Date: Tue, 26 Jun 2012 19:01:14 -0400 [thread overview]
Message-ID: <CAD2Ti2_7dc00bad0stAzYHgPG9f6Y91fYodyczTch73-psk7Sw@mail.gmail.com> (raw)
In-Reply-To: <20120626141129.GA30240@vps7135.xlshosting.net>
> Additionally, such addresses are exchanged and relayed via the P2P network.
> To do so, we reused the fd87:d87e:eb43::/48 IPv6 range. Each address in this
> 80-bit range is mapped to an onion address, and treated as belonging to a
> separate network. This network range is the same as used by the OnionCat
> application (though we do not use OnionCat in any way), and is part of the
> RFC4193 Unique Local IPv6 range, which is normally not globally routable.
>
> Other clients that wish to implement similar functionality, can use this
> test case: 5wyqrzbvrdsumnok.onion == FD87:D87E:EB43:edb1:8e4:3588:e546:35ca.
> The conversion is simply decoding the base32 onion address, and storing the
> resulting 80 bits of data as low-order bits of an IPv6 address, prefixed by
> fd87:d87e:eb43:. As this range is not routable, there should be no
> compatibility problems: any unaware IPv6-capable code will immediately fail
> when trying to connect.
You are going to want to include the block of the Phatom project as well:
https://code.google.com/p/phantom/
fd00:2522:3493::/48
And the one for 'garlicat' for I2P, which might be more complex due
to I2P's addressing:
fd60:db4d:ddb5::/48
Note that while these blocks are not expected to be routable, that
people may in fact have interfaces, routing tables and packet filters
on their machines configured with up to all three of those networks
for the purposes therein.
next prev parent reply other threads:[~2012-06-26 23:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 14:11 Pieter Wuille
2012-06-26 23:01 ` grarpamp [this message]
2012-06-27 0:14 ` Gregory Maxwell
[not found] ` <CAD2Ti29tMRCoW0rBSH738=0LpMfnGSJoSGYubV2-qQ9a6SC=zQ@mail.gmail.com>
[not found] ` <4FEAA936.10300@infosecurity.ch>
[not found] ` <CAD2Ti28hu6PccXpu4ObcbzWwFq+tchYaCoVY7S=9yakaB-nKjQ@mail.gmail.com>
2012-06-27 9:25 ` [Bitcoin-development] [tor-talk] " grarpamp
2012-06-27 8:47 ` [Bitcoin-development] " Andy Parkins
2012-06-27 19:51 grarpamp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAD2Ti2_7dc00bad0stAzYHgPG9f6Y91fYodyczTch73-psk7Sw@mail.gmail.com \
--to=grarpamp@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=phantom-protocol@googlegroups$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox