📅 Original date posted:2011-07-01
🗒️ Summary of this message: Discussion on enabling UPnP in Bitcoin. Some are in favor of turning it on by default in the GUI, while others are concerned about security.
📝 Original message:On Fri, Jul 1, 2011 at 5:35 PM, <jan at uos.de> wrote:
> On Fri, Jul 01, 2011 at 11:06:56AM -0400, Gavin Andresen wrote:
> > > Not sure about OS differentiation, seems...wrong? Maybe disabled by
> > > default on bitcoind but on by default on bitcoin?
> >
> > OK. I mis-remembered the poll:
> > http://forum.bitcoin.org/index.php?topic=4392.0
> >
> > On by default 8 (20%)
> > Off by default 22 (55%)
> > On by default in the GUI, off by default in bitcoind 10 (25%)
>
> I just voted as well and now - with some extra votes in the meantime -
> it's 9 / 22 / 13. So exactly 50/50 between off (22) and some form of on
> (9 + 13).
>
> I'm in favor of turning it on by default in the GUI and leaving it off
> in bitcoind.
>
> I don't like UPnP much, I find it exemplifies exactly what is wrong with
> computer security today: Convenience trumps security almost every time.
>
> BUT: I don't think this is the moment to fight UPnP. It's the standard
> mechanism in use today to let a computer behind a NAT accept incoming
> connections. The user has already made the decision in regards to
> convenience over security. By enabling UPnP (or by buying a product that
> does this automatically) they are saying: I want it to "just work"
> instead of having fine-grained but more complicated control.
>
> Bitcoin is a P2P application and as such should use this
> mechanism. I think it's pretty clear that participating in a P2P network
> requires one to receive messages from other peers. At least no one seems
> to be concerned that Bitcoin (by default!) listens on port 8333. So I
> think it's only logical to extend that to work behind NATs as well
If bitcoin listened on IPv6 that might help for alot of people. Windows 7
users get a teredo IPv6 address (unless they disable it) when behind NAT on
IPv4. Take any win7 box and put it on a typical NAT /DSL setup this is what
happens. I think this might actually work for more users than have UPNP
support on their DSL gateways. teredo IPs aren't that stable though (they
change frequently) and they might tend to flood the address cache with stale
addresses.
Rob
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110701/195a339b/attachment.html>;
Robert McKay [ARCHIVE] /
npub1t6…he2py
2023-06-07 01:59:47
in reply to nevent1q…vt47
Author Public Key
npub1t6suh64e65qzzjtthffl6sa3cagp6k9usnx4qev4jsjzf7xud8psdhe2pyPublished at
2023-06-07 01:59:47Event JSON
{
"id": "9a53aec240b2c2bb5754514f08c033860849aba740ac892feb79c5fb85af7da0",
"pubkey": "5ea1cbeab9d50021496bba53fd43b1c7501d58bc84cd506595942424f8dc69c3",
"created_at": 1686103187,
"kind": 1,
"tags": [
[
"e",
"b259aa9a612285804c8ca826465b76b8809982948e0ab24ccddc1c8a657cc6bd",
"",
"root"
],
[
"e",
"4aec117800569884fd8ae394056aa8549fafdee5873ba95f743e1fd9607acc34",
"",
"reply"
],
[
"p",
"05766de3bdda2f0a97052d09e34a9d2cdb31ce60dd4471cbb27acbdde0bc755b"
]
],
"content": "📅 Original date posted:2011-07-01\n🗒️ Summary of this message: Discussion on enabling UPnP in Bitcoin. Some are in favor of turning it on by default in the GUI, while others are concerned about security.\n📝 Original message:On Fri, Jul 1, 2011 at 5:35 PM, \u003cjan at uos.de\u003e wrote:\n\n\u003e On Fri, Jul 01, 2011 at 11:06:56AM -0400, Gavin Andresen wrote:\n\u003e \u003e \u003e Not sure about OS differentiation, seems...wrong? Maybe disabled by\n\u003e \u003e \u003e default on bitcoind but on by default on bitcoin?\n\u003e \u003e\n\u003e \u003e OK. I mis-remembered the poll:\n\u003e \u003e http://forum.bitcoin.org/index.php?topic=4392.0\n\u003e \u003e\n\u003e \u003e On by default 8 (20%)\n\u003e \u003e Off by default 22 (55%)\n\u003e \u003e On by default in the GUI, off by default in bitcoind 10 (25%)\n\u003e\n\u003e I just voted as well and now - with some extra votes in the meantime -\n\u003e it's 9 / 22 / 13. So exactly 50/50 between off (22) and some form of on\n\u003e (9 + 13).\n\u003e\n\u003e I'm in favor of turning it on by default in the GUI and leaving it off\n\u003e in bitcoind.\n\u003e\n\u003e I don't like UPnP much, I find it exemplifies exactly what is wrong with\n\u003e computer security today: Convenience trumps security almost every time.\n\u003e\n\u003e BUT: I don't think this is the moment to fight UPnP. It's the standard\n\u003e mechanism in use today to let a computer behind a NAT accept incoming\n\u003e connections. The user has already made the decision in regards to\n\u003e convenience over security. By enabling UPnP (or by buying a product that\n\u003e does this automatically) they are saying: I want it to \"just work\"\n\u003e instead of having fine-grained but more complicated control.\n\u003e\n\u003e Bitcoin is a P2P application and as such should use this\n\u003e mechanism. I think it's pretty clear that participating in a P2P network\n\u003e requires one to receive messages from other peers. At least no one seems\n\u003e to be concerned that Bitcoin (by default!) listens on port 8333. So I\n\u003e think it's only logical to extend that to work behind NATs as well\n\n\nIf bitcoin listened on IPv6 that might help for alot of people. Windows 7\nusers get a teredo IPv6 address (unless they disable it) when behind NAT on\nIPv4. Take any win7 box and put it on a typical NAT /DSL setup this is what\nhappens. I think this might actually work for more users than have UPNP\nsupport on their DSL gateways. teredo IPs aren't that stable though (they\nchange frequently) and they might tend to flood the address cache with stale\naddresses.\n\nRob\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20110701/195a339b/attachment.html\u003e",
"sig": "318b03a7d786066bb1c95480f79f0ffa421eff49203e6be1c296a485cd7217b56dd3e3311b765fb9c7f74546eac1612ebb05948771b1455bad6e7a79acbcb77f"
}