📅 Original date posted:2021-03-20 📝 Original message:Hi Erik, Would ...

Arik Sosman [ARCHIVE] /

npub1dje…8qlm

2023-06-07 18:30:59

in reply to nevent1q…08an

📅 Original date posted:2021-03-20
📝 Original message:Hi Erik,

Would sha256-hmac(nonce, publicKeyPoint) still be a suitable/safe alternative without relying on sha3? That should at the very least eliminate length extension attacks.

Best,
Arik

> On Mar 19, 2021, at 6:32 PM, Erik Aronesty via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
>
> use sha3-256. sha256 suffers from certain attacks (length extension,
> for example) that could make your scheme vulnerable to leaking info,
> depending on how you concatenate things, etc. better to choose
> something where padding doesn't matter.
>
> On Fri, Mar 19, 2021 at 7:28 PM vjudeu via bitcoin-dev
> <bitcoin-dev at lists.linuxfoundation.org> wrote:
>>
>> I recently found some interesting and simple HD wallet design here: https://bitcointalk.org/index.php?topic=5321992.0
>> Could anyone see any flaws in such design or is it safe enough to implement it and use in practice?
>> If I understand it correctly, it is just pure ECDSA and SHA-256, nothing else:
>>
>> masterPublicKey = masterPrivateKey * G
>> masterChildPublicKey = masterPublicKey + ( SHA-256( masterPublicKey || nonce ) mod n ) * G
>> masterChildPrivateKey = masterPrivateKey + ( SHA-256( masterPublicKey || nonce ) mod n )
>>
>> Also, it has some nice properties, like all keys starting with 02 prefix and allows potentially unlimited custom derivation path by using 256-bit nonce.
>> _______________________________________________
>> bitcoin-dev mailing list
>> bitcoin-dev at lists.linuxfoundation.org
>> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210319/194c9b22/attachment.sig>;

Author Public Key

npub1dje2hdnptk0k4gr5rt73vycxhc7xkkskyj32p6mgvhx66wltl76q268qlm

Show more details

Published at

2023-06-07 18:30:59

Kind type

1 Short Text Note

Event JSON

{ "id": "f29fa0d18cf6676426c01205669388f5607d806d403762c46f1fc88e041ad6e6", "pubkey": "6cb2abb6615d9f6aa0741afd161306be3c6b5a1624a2a0eb6865cdad3bebffb4", "created_at": 1686162659, "kind": 1, "tags": [ [ "e", "69708790841c33eb579cf900d3977a71d1f4f272db7c13d1670b70f61a12c1cb", "", "root" ], [ "e", "1dfaa49052bab6b3fe8ce84370583a1991ce662c05c91b749a82a4cca296183d", "", "reply" ], [ "p", "22944ce1e29904e3826d25013a614e4665693ec514003efacc1b7586e8e5d0aa" ] ], "content": "📅 Original date posted:2021-03-20\n📝 Original message:Hi Erik,\n\nWould sha256-hmac(nonce, publicKeyPoint) still be a suitable/safe alternative without relying on sha3? That should at the very least eliminate length extension attacks.\n\nBest,\nArik\n\n\u003e On Mar 19, 2021, at 6:32 PM, Erik Aronesty via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e use sha3-256. sha256 suffers from certain attacks (length extension,\n\u003e for example) that could make your scheme vulnerable to leaking info,\n\u003e depending on how you concatenate things, etc. better to choose\n\u003e something where padding doesn't matter.\n\u003e \n\u003e On Fri, Mar 19, 2021 at 7:28 PM vjudeu via bitcoin-dev\n\u003e \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e\u003e \n\u003e\u003e I recently found some interesting and simple HD wallet design here: https://bitcointalk.org/index.php?topic=5321992.0\n\u003e\u003e Could anyone see any flaws in such design or is it safe enough to implement it and use in practice?\n\u003e\u003e If I understand it correctly, it is just pure ECDSA and SHA-256, nothing else:\n\u003e\u003e \n\u003e\u003e masterPublicKey = masterPrivateKey * G\n\u003e\u003e masterChildPublicKey = masterPublicKey + ( SHA-256( masterPublicKey || nonce ) mod n ) * G\n\u003e\u003e masterChildPrivateKey = masterPrivateKey + ( SHA-256( masterPublicKey || nonce ) mod n )\n\u003e\u003e \n\u003e\u003e Also, it has some nice properties, like all keys starting with 02 prefix and allows potentially unlimited custom derivation path by using 256-bit nonce.\n\u003e\u003e _______________________________________________\n\u003e\u003e bitcoin-dev mailing list\n\u003e\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: Message signed with OpenPGP\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20210319/194c9b22/attachment.sig\u003e", "sig": "2401381ff97ea9c44ab51b3a9bad5660e48bb885c55a27d97bfa8d06ffe839670d2de2030051ce8c5024f5c10665196f47f4de6eccb4221a8bc6abc539c9cb4c" }