Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QpJ4U-0004GQ-L6 for bitcoin-development@lists.sourceforge.net; Fri, 05 Aug 2011 12:00:10 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bluematt.me designates 173.246.101.161 as permitted sender) client-ip=173.246.101.161; envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1QpJ4T-0004v9-Sj for bitcoin-development@lists.sourceforge.net; Fri, 05 Aug 2011 12:00:10 +0000 Received: from [IPv6:2001:470:9ff2:1:ee55:f9ff:fec6:e666] (unknown [IPv6:2001:470:9ff2:1:ee55:f9ff:fec6:e666]) by mail.bluematt.me (Postfix) with ESMTPSA id B6E2E2F19 for ; Fri, 5 Aug 2011 13:59:59 +0200 (CEST) From: Matt Corallo To: bitcoin-development@lists.sourceforge.net In-Reply-To: <4E3B35E7.1010409@justmoon.de> References: <201108041423.14176.andyparkins@gmail.com> <201108041922.16956.andyparkins@gmail.com> <1312483196.3109.38.camel@Desktop666> <201108042042.55214.andyparkins@gmail.com> <1312496173.3109.55.camel@Desktop666> <4E3B35E7.1010409@justmoon.de> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-lA9af7LknCl+EXmieEXS" Date: Fri, 05 Aug 2011 14:00:02 +0200 Message-ID: <1312545602.4516.3.camel@BMThinkPad.lan.bluematt.me> Mime-Version: 1.0 X-Mailer: Evolution 2.32.2 X-Spam-Score: -2.4 (--) 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 SPF_PASS SPF: sender matches SPF record -0.9 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1QpJ4T-0004v9-Sj Subject: Re: [Bitcoin-development] Double spend detection to speed up transaction trust 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, 05 Aug 2011 12:00:10 -0000 --=-lA9af7LknCl+EXmieEXS Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2011-08-05 at 02:14 +0200, Stefan Thomas wrote: > (I know Bitcoin has UPnP support,=20 > but I haven't found any numbers on how widely the IGD protocol is=20 > actually deployed. Wikipedia says that "some NAT routers" support it and= =20 > that it's not an IETF standard. All routers I've actually seen in real= =20 > life had it disabled by default.) It used to be enabled by default on virtually all routers a couple years ago, but too many "security researchers" complained that it was a "huge security vulnerability" (I guess they hadn't heard of stun or outgoing connections) so its not typically disabled on most routers. --=-lA9af7LknCl+EXmieEXS Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAABAgAGBQJOO9tAAAoJEBrh01BD4I5ULpwP/3w3vpn6yqmzvj98P5mWN7th 0sFKF3+s4vF4XItWsD4xP++GZPr/+7Y7sgDC8EfKyTDXcbQObCcu0UU0iFlTyJEV EXzwfvW/B1vdNw7JldMOUdiLttyMwZFMsi42+UlQ6QhbH8QyA0pG2hrfNaBIx6be ENpMj5mN37760sjI7V0M8w/1JzVVmQNZbdBibrxe4vnR9EsESiPXHJAskSm+hLS1 5LiH4B/gV6GSpZFS+og76n1EpyBWD/i+jtAWfbhMQWLIYDOH3UH6/6GGyQPEJW3D dnITRo7L92olzouSNxf448JWSribRBpwG9fTydh4K1WTZtZLSR7rGb5nAdi/8m0t HRA3FCblpwVQqV3nvvn5W+lisgr1hvGExV03v9U2i0rVs6MDmuni2tSKz0QhSMQf hUXT+dhZgenzdSUsDVI9qEkS2cAw8FSrG0HyIkU1yBNoSCOqhZVXtVwkgIgPCagj Su0nbneaWATf0V7u3GWycQE7v1VsduantdszVaZUxoLyBw3JEXw9uC9VjeJQ3IiK mLZtbvEFt0JCqCrkug1R0bZ5hsgdHRJNMZYrUVdtRuPojn4U23qPVVOk68AaWRqO wu3+OGYu4LxTvbssirsClGkNqyLKh6ceudPyZ8b19PbAJi0TaIg/C/uFTSNpzVoE IHprP/NXo28PagV6PisW =8F6v -----END PGP SIGNATURE----- --=-lA9af7LknCl+EXmieEXS--