馃搮 Original date posted:2014-08-19
馃摑 Original message:Oh, I see. I misread, thinking you wanted the dev team to have a private key and share the public key, similar to alerts. But each peer would have a public/private key pair and use something akin to ECDH for a symmetric key and transport using a block cipher?
How would you share the public key? If I were a man-in-the-middle, I could intercept the public key, generate my own and pass that along and then decouple the pipe when the other side shares their public key.
Also, you should not ignore your SSH fingerprint, as you exactly open yourself to mitm attacks.
On Aug 19, 2014, at 11:11 AM, Ra煤l Mart铆nez <rme at i-rme.es> wrote:
> Only messages between peers are encrypted, only during transit.
>
> Before sending a transaction to Node B you use his public key, so Node B has the key
>
> El 19/08/2014 17:05, "Richard Moore" <me at ricmoo.com> escribi贸:
> If you encrypt all messages with an asymmetric cipher, how would each node make use of the blockchain in an encrypted form? Each node would be able to encrypt the data, but only the Bitcoin Core Dev could decrypt it?
>
>
> On Aug 19, 2014, at 5:49 AM, Ra煤l Mart铆nez <rme at i-rme.es> wrote:
>
>> Hi,
>> I believe that all comunications should be encrypted by default, no matter that is public information (tx info), the only exception I would make would be block packets (to avoid increasing propagation time).
>>
>> I suggest that Bitcoin Core should generate a public/private key pair and share the public one with peers.
>>
>> This could provide privacy and integrity but not autentication.
>>
>> This way you can impersonate a bitcoin node (active mitm) but you cant just be passive and record all transactions send or recieved by an IP address.
>>
>> Today you can just watch for incoming/outgoing transactions to determine what tx are created in the Node, when you find one you can see the Bitcoin address inputs and outputs and track that person's bitcoins.
>> As an example, SSH provides this kind of encryption, althogh Bitcoin Core should ignore fingerprint changes (caused due to reinstalls).
>>
>> Please feel free to disqus why this is not needed or why you like this idea.
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Bitcoin-development mailing list
>> Bitcoin-development at lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
> .路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂><(((潞>
>
> Richard Moore ~ Founder
> Genetic Mistakes Software inc.
> phone: (778) 882-6125
> email: ricmoo at geneticmistakes.com
> www: http://GeneticMistakes.com
>
.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂><(((潞>
Richard Moore ~ Founder
Genetic Mistakes Software inc.
phone: (778) 882-6125
email: ricmoo at geneticmistakes.com
www: http://GeneticMistakes.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140819/6f49bfd8/attachment.html>;
Richard Moore [ARCHIVE] /
npub1rx鈥etyf
2023-06-07 15:25:18
in reply to nevent1q鈥t3l
Author Public Key
npub1rxqlcf4n2aw0urx6l4g7rjkyng8d5w0lkqphnaycrchyh3dwktzsejetyfPublished at
2023-06-07 15:25:18Event JSON
{
"id": "4abe7b38ff96f17747f1538e3eaed31284168504bc75c93858b6b7cb5f42f528",
"pubkey": "1981fc26b3575cfe0cdafd51e1cac49a0eda39ffb00379f4981e2e4bc5aeb2c5",
"created_at": 1686151518,
"kind": 1,
"tags": [
[
"e",
"f7d80207f3f3e09247c97d3e8c17b8e8b9ffc855be5e4ac09f019815084b2528",
"",
"root"
],
[
"e",
"3765f9a5b07783279a1689daa23162f1824bc846f3ca5c9a55f6b891c61c98fc",
"",
"reply"
],
[
"p",
"71ecb20159fc921d3fdd5cadaf19452674dafcfc436a55b91b0f0139fb23e115"
]
],
"content": "馃搮 Original date posted:2014-08-19\n馃摑 Original message:Oh, I see. I misread, thinking you wanted the dev team to have a private key and share the public key, similar to alerts. But each peer would have a public/private key pair and use something akin to ECDH for a symmetric key and transport using a block cipher?\n\nHow would you share the public key? If I were a man-in-the-middle, I could intercept the public key, generate my own and pass that along and then decouple the pipe when the other side shares their public key.\n\nAlso, you should not ignore your SSH fingerprint, as you exactly open yourself to mitm attacks.\n\n\n\nOn Aug 19, 2014, at 11:11 AM, Ra煤l Mart铆nez \u003crme at i-rme.es\u003e wrote:\n\n\u003e Only messages between peers are encrypted, only during transit.\n\u003e \n\u003e Before sending a transaction to Node B you use his public key, so Node B has the key\n\u003e \n\u003e El 19/08/2014 17:05, \"Richard Moore\" \u003cme at ricmoo.com\u003e escribi贸:\n\u003e If you encrypt all messages with an asymmetric cipher, how would each node make use of the blockchain in an encrypted form? Each node would be able to encrypt the data, but only the Bitcoin Core Dev could decrypt it?\n\u003e \n\u003e \n\u003e On Aug 19, 2014, at 5:49 AM, Ra煤l Mart铆nez \u003crme at i-rme.es\u003e wrote:\n\u003e \n\u003e\u003e Hi,\n\u003e\u003e I believe that all comunications should be encrypted by default, no matter that is public information (tx info), the only exception I would make would be block packets (to avoid increasing propagation time).\n\u003e\u003e \n\u003e\u003e I suggest that Bitcoin Core should generate a public/private key pair and share the public one with peers.\n\u003e\u003e \n\u003e\u003e This could provide privacy and integrity but not autentication.\n\u003e\u003e \n\u003e\u003e This way you can impersonate a bitcoin node (active mitm) but you cant just be passive and record all transactions send or recieved by an IP address.\n\u003e\u003e \n\u003e\u003e Today you can just watch for incoming/outgoing transactions to determine what tx are created in the Node, when you find one you can see the Bitcoin address inputs and outputs and track that person's bitcoins.\n\u003e\u003e As an example, SSH provides this kind of encryption, althogh Bitcoin Core should ignore fingerprint changes (caused due to reinstalls).\n\u003e\u003e \n\u003e\u003e Please feel free to disqus why this is not needed or why you like this idea.\n\u003e\u003e \n\u003e\u003e ------------------------------------------------------------------------------\n\u003e\u003e _______________________________________________\n\u003e\u003e Bitcoin-development mailing list\n\u003e\u003e Bitcoin-development at lists.sourceforge.net\n\u003e\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e \n\u003e .路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂\u003e\u003c(((潞\u003e\n\u003e \n\u003e Richard Moore ~ Founder\n\u003e Genetic Mistakes Software inc.\n\u003e phone: (778) 882-6125\n\u003e email: ricmoo at geneticmistakes.com\n\u003e www: http://GeneticMistakes.com\n\u003e \n\n.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂赂.路麓炉`路.赂\u003e\u003c(((潞\u003e\n\nRichard Moore ~ Founder\nGenetic Mistakes Software inc.\nphone: (778) 882-6125\nemail: ricmoo at geneticmistakes.com\nwww: http://GeneticMistakes.com\n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140819/6f49bfd8/attachment.html\u003e",
"sig": "6e50d4efea6d6041a4d1ec1010c53e9c1ca5e82c4bfe5bacdc6c8d4ff4f38abe403457d076667e41bd7e80d2744dafa7193d982b55488f2f94c60863ec8b2012"
}