📅 Original date posted:2014-08-19
📝 Original message:"I suggest that Bitcoin Core should generate a public/private key pair and
share the public one with peers."
I've not read the p2p protocol of Bitcoin core, but I suppose the initial
handshake between 2 peers would be the ideal place to exchange a public
keys.
would it make sense to generate a new random pair of keys per each peer you
connect to?
then each subsequent message to every peer gets encrypted differently,
keeping each conversation isolated from each other encryption-speaking.
These keys would have nothing to do with your wallet, they're just to
encrypt any further communication between peers post-handshake. Would that
be of any use to "This could provide privacy and integrity but not
autentication."?
http://twitter.com/gubatron
On Tue, Aug 19, 2014 at 12:38 PM, Gregory Maxwell <gmaxwell at gmail.com>
wrote:
> On Tue, Aug 19, 2014 at 9:07 AM, Justus Ranvier
> <justusranvier at riseup.net> wrote:
> > If that's not acceptable, even using TLS with self-signed certificates
> > would be an improvement.
>
> TLS is a huge complex attack surface, any use of it requires an
> additional dependency with a large amount of difficult to audit code.
> TLS is trivially DOS attacked and every major/widely used TLS
> implementation has had multiple memory disclosure or remote execution
> vulnerabilities even in just the last several years.
>
> We've dodged several emergency scale vulnerabilities by not having TLS.
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140819/5903b960/attachment.html>;
Angel Leon [ARCHIVE] /
npub1c8…zgzt8
2023-06-07 15:25:19
in reply to nevent1q…0qg2
Author Public Key
npub1c8flqlwmkh5vehm7rfcacurk9x5ggv36vtra2p97thynzfq0vxus5zgzt8Published at
2023-06-07 15:25:19Event JSON
{
"id": "a677b015796704fb7214bd9da0712b95a3e6525bd03840cca56c84c5ceb07e4c",
"pubkey": "c1d3f07ddbb5e8ccdf7e1a71dc707629a884323a62c7d504be5dc931240f61b9",
"created_at": 1686151519,
"kind": 1,
"tags": [
[
"e",
"f7d80207f3f3e09247c97d3e8c17b8e8b9ffc855be5e4ac09f019815084b2528",
"",
"root"
],
[
"e",
"9f7c0ec97c55836657344e79dc58dd0b637f11c53aa16dd25fb77becd5ca5236",
"",
"reply"
],
[
"p",
"4aa6cf9aa5c8e98f401dac603c6a10207509b6a07317676e9d6615f3d7103d73"
]
],
"content": "📅 Original date posted:2014-08-19\n📝 Original message:\"I suggest that Bitcoin Core should generate a public/private key pair and\nshare the public one with peers.\"\n\nI've not read the p2p protocol of Bitcoin core, but I suppose the initial\nhandshake between 2 peers would be the ideal place to exchange a public\nkeys.\n\nwould it make sense to generate a new random pair of keys per each peer you\nconnect to?\nthen each subsequent message to every peer gets encrypted differently,\nkeeping each conversation isolated from each other encryption-speaking.\n\nThese keys would have nothing to do with your wallet, they're just to\nencrypt any further communication between peers post-handshake. Would that\nbe of any use to \"This could provide privacy and integrity but not\nautentication.\"?\n\nhttp://twitter.com/gubatron\n\n\nOn Tue, Aug 19, 2014 at 12:38 PM, Gregory Maxwell \u003cgmaxwell at gmail.com\u003e\nwrote:\n\n\u003e On Tue, Aug 19, 2014 at 9:07 AM, Justus Ranvier\n\u003e \u003cjustusranvier at riseup.net\u003e wrote:\n\u003e \u003e If that's not acceptable, even using TLS with self-signed certificates\n\u003e \u003e would be an improvement.\n\u003e\n\u003e TLS is a huge complex attack surface, any use of it requires an\n\u003e additional dependency with a large amount of difficult to audit code.\n\u003e TLS is trivially DOS attacked and every major/widely used TLS\n\u003e implementation has had multiple memory disclosure or remote execution\n\u003e vulnerabilities even in just the last several years.\n\u003e\n\u003e We've dodged several emergency scale vulnerabilities by not having TLS.\n\u003e\n\u003e\n\u003e ------------------------------------------------------------------------------\n\u003e _______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140819/5903b960/attachment.html\u003e",
"sig": "5ebee510a110e38a1e33f2bdc657d93a0ab931e6fd86a8b838193a37350df95cbaeaa04167456cba0b7d55ca4251c9242a465eea6d0e9e2cb0de8873e29a6d4e"
}