From: Gregory Maxwell <gmaxwell@gmail•com>
To: grarpamp <grarpamp@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net,
phantom-protocol@googlegroups•com
Subject: Re: [Bitcoin-development] Tor hidden service support
Date: Tue, 26 Jun 2012 20:14:08 -0400 [thread overview]
Message-ID: <CAAS2fgQEcNOwfw9YkN-jJZi_pb4Ex3ujY4KgWzL07=BVVknt_w@mail.gmail.com> (raw)
In-Reply-To: <CAD2Ti2_7dc00bad0stAzYHgPG9f6Y91fYodyczTch73-psk7Sw@mail.gmail.com>
On Tue, Jun 26, 2012 at 7:01 PM, grarpamp <grarpamp@gmail•com> wrote:
> 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
Perhaps some argument to add blocks to the IsRoutable check is in
order? Then people who use overlay networks that are actually
routable but which use otherwise private space can just add the
relevant blocks.
> 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.
Note that while the hidden service support in bitcoin uses a
compatible IPv6 mapping with onioncat, it is _not_ onioncat, does not
use onioncat, does not need onioncat, and wouldn't benefit from
onioncat. The onioncat style advertisement is used because our
protocol already relays IPv6 addresses. The connections are regular
tor hidden service connections, not the more-risky and low performance
ip in tcp onioncat stuff.
next prev parent reply other threads:[~2012-06-27 0:14 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
2012-06-27 0:14 ` Gregory Maxwell [this message]
[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='CAAS2fgQEcNOwfw9YkN-jJZi_pb4Ex3ujY4KgWzL07=BVVknt_w@mail.gmail.com' \
--to=gmaxwell@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=grarpamp@gmail$(echo .)com \
--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