If you store the same private key on both a Trezor and a Ledger, you expose it to vulnerabilities on both stacks. So Ledger using a closed source "Secure Element" might have given you an insecure private key as there is no way for a public audit to rule this out. Copying a weak key to a Trezor now exposes it to Trezor's extractability.
You did not reduce your risk. You squared it.
Leo Wandersleb
npub1gm…78rf6
2023-09-18 16:22:41
in reply to nevent1q…9vav
Author Public Key
npub1gm7tuvr9atc6u7q3gevjfeyfyvmrlul4y67k7u7hcxztz67ceexs078rf6Published at
2023-09-18 16:22:41Event JSON
{
"id": "01a104b427364e2e490bb2df26426190df386fe0154b540ba9b05bcf21e1a7fc",
"pubkey": "46fcbe3065eaf1ae7811465924e48923363ff3f526bd6f73d7c184b16bd8ce4d",
"created_at": 1695054161,
"kind": 1,
"tags": [
[
"e",
"de6fbaf04446bb119eb73bf7d9f7e2edb193d17f55db8245c8677b0923f13a60",
"",
"reply"
],
[
"p",
"700d3de34b2929478652de1a41738ea4b3589831a76d1adfc612bd6f2529fd22"
]
],
"content": "If you store the same private key on both a Trezor and a Ledger, you expose it to vulnerabilities on both stacks. So Ledger using a closed source \"Secure Element\" might have given you an insecure private key as there is no way for a public audit to rule this out. Copying a weak key to a Trezor now exposes it to Trezor's extractability.\n\nYou did not reduce your risk. You squared it.",
"sig": "d846018d1543facaf9a3551770635a7db30cb4e11297e34f4d1e28ca927ab26c800fce7b9f15b326ec73be66c87837d2495356b0e58170310ad5f68d312fab9e"
}