Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XFke4-0007wa-Fj for bitcoin-development@lists.sourceforge.net; Fri, 08 Aug 2014 13:55:48 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.219.48 as permitted sender) client-ip=209.85.219.48; envelope-from=mh.in.england@gmail.com; helo=mail-oa0-f48.google.com; Received: from mail-oa0-f48.google.com ([209.85.219.48]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XFke3-000679-J4 for bitcoin-development@lists.sourceforge.net; Fri, 08 Aug 2014 13:55:48 +0000 Received: by mail-oa0-f48.google.com with SMTP id m1so4019383oag.7 for ; Fri, 08 Aug 2014 06:55:42 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.182.224.227 with SMTP id rf3mr30714176obc.70.1407506142144; Fri, 08 Aug 2014 06:55:42 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.76.35.234 with HTTP; Fri, 8 Aug 2014 06:55:42 -0700 (PDT) In-Reply-To: References: Date: Fri, 8 Aug 2014 15:55:42 +0200 X-Google-Sender-Auth: cLgropYW0OFcZpRF9sYYyjoR_8k Message-ID: From: Mike Hearn To: Wladimir Content-Type: multipart/alternative; boundary=089e013a05de9f336c05001e8fcd X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1XFke3-000679-J4 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] NODE_EXT_SERVICES and advertising related services X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2014 13:55:48 -0000 --089e013a05de9f336c05001e8fcd Content-Type: text/plain; charset=UTF-8 > > 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. Yes, can be done this way too. I was thinking about setups where you have services distributed across multiple machines. However a separate port does indeed allow iptables or the like to be used. --089e013a05de9f336c05001e8fcd Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'd be OK with such an idea if bitcoind list= ens 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.

Yes, can be done this way too. I was thinking about s= etups where you have services distributed across multiple machines. However= a separate port does indeed allow iptables or the like to be used.=C2=A0
--089e013a05de9f336c05001e8fcd--