Sjors Provoost [ARCHIVE] on Nostr: 📅 Original date posted:2017-09-30 📝 Original message:> Op 30 sep. 2017, om ...
📅 Original date posted:2017-09-30
📝 Original message:> Op 30 sep. 2017, om 06:49 heeft Jonas Schnelli via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> het volgende geschreven:
>
>> On 09/29/2017 02:03 PM, Luke Dashjr wrote:
>> Paper wallets are a safety hazard, insecure, and generally not advisable.
>>
>
> I have to agree with Luke.
> And I would also extend those concerns to BIP39 plaintext paper backups.
>
> IMO, private keys should be generated and used (signing) on a trusted, minimal and offline hardware/os. They should never leave the device over the channel used for the signing I/O. Users should have no way to view or export the private keys (expect for the seed backup). Backups should be encrypted (whoever finds the paper backup should need a second factor to decrypt) and the restore process should be footgun-safe (especially the lost-passphrase deadlock).
I believe BIP39 does an excellent job at reducing the amount of bitcoin permanently lost. Stolen funds can at least in theory be retrieved at some future date. There's a trade-off between having a backup process that is secure and one that people actually use. I don't know the right answer, and tend to agree it's better left to individual wallets to decide.
Sjors
-------------- 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/20170930/d70b17b5/attachment-0001.sig>
Published at
2023-06-07 18:06:42Event JSON
{
"id": "40b6d85427f45bae30d8752ddfe5c527763abf834510b394d95f9e9f57c561b0",
"pubkey": "e1ad0d0d83103f222425541294008149d215c1e1629b0bb37b98e19f698feb3e",
"created_at": 1686161202,
"kind": 1,
"tags": [
[
"e",
"adbe104cdeb184e2b9ee2e7441c0306f637c427dfa72914e557b36050055e79e",
"",
"root"
],
[
"e",
"3064cc7e6a03dfb587b1e82bb688a44a677c99c0c77dc25320aec9a117fc72a1",
"",
"reply"
],
[
"p",
"a2711d6616d348a3542bb2a791a9e51fcbc7b7d1d20652e5abe16d3e179321df"
]
],
"content": "📅 Original date posted:2017-09-30\n📝 Original message:\u003e Op 30 sep. 2017, om 06:49 heeft Jonas Schnelli via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e het volgende geschreven:\n\u003e \n\u003e\u003e On 09/29/2017 02:03 PM, Luke Dashjr wrote:\n\u003e\u003e Paper wallets are a safety hazard, insecure, and generally not advisable.\n\u003e\u003e \n\u003e \n\u003e I have to agree with Luke.\n\u003e And I would also extend those concerns to BIP39 plaintext paper backups.\n\u003e \n\u003e IMO, private keys should be generated and used (signing) on a trusted, minimal and offline hardware/os. They should never leave the device over the channel used for the signing I/O. Users should have no way to view or export the private keys (expect for the seed backup). Backups should be encrypted (whoever finds the paper backup should need a second factor to decrypt) and the restore process should be footgun-safe (especially the lost-passphrase deadlock).\n\nI believe BIP39 does an excellent job at reducing the amount of bitcoin permanently lost. Stolen funds can at least in theory be retrieved at some future date. There's a trade-off between having a backup process that is secure and one that people actually use. I don't know the right answer, and tend to agree it's better left to individual wallets to decide.\n\nSjors\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/20170930/d70b17b5/attachment-0001.sig\u003e",
"sig": "4b476c1bbb50d5a15bf2d7dc304fa1b7e60e20e2ecd6c95cbb78a76df3b4bf03ddc6c83921eaaf74ddffd5d68207344d5b005f6c325ba0e6fc06850a2d597bf0"
}