š
Original date posted:2016-08-16
š Original message:On Wed, Aug 17, 2016 at 09:36:02AM +1000, Aiqin Li via bitcoin-dev wrote:
> Out of curiosity, what is the technical reason a normal ECC-enabled
> smart-card cannot be used for the hardware signing component of a wallet
> app? (Since if it can, its standardization must have been discussed.)
>
> Debian wiki gives a list of such cards with related opensource software to
> access them.
I'm not aware of any ECC-enabled smart-cards that can sign the specific curve
that Bitcoin uses, not to mention the fact that those smartcards generally only
speak higher level protocols than raw signature generation, precluding the
signing of bitcoin transactions.
The other serious problem - and this is a problem with smartcards in general
anyway - is that without Bitcoin-specific logic you're just signing blindly; we
recently saw the problems with that with the Bitfinex/BitGo hack. And even
then, without a screen most of the hardware wallets in are still just signing
blindly, with at best hard-to-use limits on maximum funds moved
per-transaction. Also note how even hardware wallets with a screen, like
Trezor, aren't yet able to authenticate who you are paying.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160816/29699c7e/attachment.sig>;
Peter Todd [ARCHIVE] /
npub1m2ā¦a2np2
2023-06-07 17:52:54
in reply to nevent1qā¦a6qk
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 17:52:54Event JSON
{
"id": "bab9b531be8b2e9c1f86c0835c90a57b1042a61a2af62cbc994353a1fca83e2c",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686160374,
"kind": 1,
"tags": [
[
"e",
"6e7f7cb2c3110cb7289a3abd667304a3b4e6f9ba4e2581c492d7b93c214a5ea1",
"",
"root"
],
[
"e",
"abf7e8ef4e230bfa5b865f9a4f99d76c042df98a6909b143cc3df027f6d53bc7",
"",
"reply"
],
[
"p",
"95233cebbfc0021bee31ded87a6b7bace48130ba4dd012ee13fa38e0579dccfc"
]
],
"content": "š
Original date posted:2016-08-16\nš Original message:On Wed, Aug 17, 2016 at 09:36:02AM +1000, Aiqin Li via bitcoin-dev wrote:\n\u003e Out of curiosity, what is the technical reason a normal ECC-enabled\n\u003e smart-card cannot be used for the hardware signing component of a wallet\n\u003e app? (Since if it can, its standardization must have been discussed.)\n\u003e \n\u003e Debian wiki gives a list of such cards with related opensource software to\n\u003e access them.\n\nI'm not aware of any ECC-enabled smart-cards that can sign the specific curve\nthat Bitcoin uses, not to mention the fact that those smartcards generally only\nspeak higher level protocols than raw signature generation, precluding the\nsigning of bitcoin transactions.\n\nThe other serious problem - and this is a problem with smartcards in general\nanyway - is that without Bitcoin-specific logic you're just signing blindly; we\nrecently saw the problems with that with the Bitfinex/BitGo hack. And even\nthen, without a screen most of the hardware wallets in are still just signing\nblindly, with at best hard-to-use limits on maximum funds moved\nper-transaction. Also note how even hardware wallets with a screen, like\nTrezor, aren't yet able to authenticate who you are paying.\n\n-- \nhttps://petertodd.org 'peter'[:-1]@petertodd.org\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 455 bytes\nDesc: Digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160816/29699c7e/attachment.sig\u003e",
"sig": "e7b85158244f0b109a2aa6680af30cf01a8d79913dc9d0a7dee4752ce4ee29aaa93e3720acbb31f9254decd5b27a06f24ba68d244ac6d68c42b6641321eda297"
}