From: Wladimir <laanwj@gmail•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related services
Date: Fri, 8 Aug 2014 14:34:32 +0200 [thread overview]
Message-ID: <CA+s+GJBuyn2xYeBoh9r4E=qjHdrti6u1K6cApYbgROs2CpPukQ@mail.gmail.com> (raw)
In-Reply-To: <CANEZrP2UFMDJ+88MU=RTyU4FV_HCHwuHLmd5S9aK2AZ7DJ+j7g@mail.gmail.com>
On Fri, Aug 8, 2014 at 2:11 PM, Mike Hearn <mike@plan99•net> wrote:
> Maybe, that feels like it could be overkill though. Probably just something
> like
>
> ./bitcoind -servicecookie=<long random string> -allowextservices=127.0.0.1/8
I don't like conflating the external and internal interface. The
interface to the outside and the interface to the inside should be
well-separated.
I'd be OK with such an idea if bitcoind listens on a separate port for
connections from plugins, a port that cannot be used for normal P2P
traffic. This could also be a UNIX socket instead of a TCP port.
Wladimir
next prev parent reply other threads:[~2014-08-08 12:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 3:38 Jeff Garzik
2014-08-08 9:45 ` Mike Hearn
2014-08-08 9:56 ` Wladimir
2014-08-08 10:01 ` Mike Hearn
2014-08-08 10:15 ` Wladimir
2014-08-08 10:26 ` Wladimir
2014-08-08 10:41 ` Christian Decker
2014-08-08 11:22 ` Jeff Garzik
2014-08-08 11:33 ` Jeff Garzik
2014-08-08 11:38 ` Mike Hearn
2014-08-08 11:59 ` Wladimir
2014-08-08 12:06 ` Jeff Garzik
2014-08-08 12:11 ` Jeff Garzik
2014-08-08 12:15 ` Wladimir
2014-08-08 12:11 ` Mike Hearn
2014-08-08 12:15 ` Jeff Garzik
2014-08-08 12:16 ` Wladimir
2014-08-08 12:34 ` Wladimir [this message]
2014-08-08 13:55 ` Mike Hearn
2014-08-08 12:04 ` Jeff Garzik
2014-08-08 12:13 ` Mike Hearn
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='CA+s+GJBuyn2xYeBoh9r4E=qjHdrti6u1K6cApYbgROs2CpPukQ@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/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