A on Nostr: #ledger #[1] Correct me if I’m wrong but code now exists that opens a door into ...
#ledger
NVK (npub1az9…m8y8)
Correct me if I’m wrong but code now exists that opens a door into the secure element of a ledger device to extract information. Regardless of how that information is handled and processed, there’s a door.
The service being provided isn’t the problem, the problem is the door. People didn’t know it existed, should we have known? Is this normal, do all secure elements have a door that can be accessed with simple firmware update.
I personally thought that physical access was the only way to extract information from the secure element.
Published at
2023-05-16 15:50:16Event JSON
{
"id": "fa6357bbfeeee6d99dc71d162acd12b6f4eed6e9f20a5f86b7f65f522eaabb6b",
"pubkey": "0bdea4325be1cbe8ba0f2d37e97bb7f77f693808569e1500d36e754074932730",
"created_at": 1684252216,
"kind": 1,
"tags": [
[
"t",
"ledger"
],
[
"p",
"e88a691e98d9987c964521dff60025f60700378a4879180dcbbb4a5027850411"
]
],
"content": "#ledger \n#[1] \n\nCorrect me if I’m wrong but code now exists that opens a door into the secure element of a ledger device to extract information. Regardless of how that information is handled and processed, there’s a door. \n\nThe service being provided isn’t the problem, the problem is the door. People didn’t know it existed, should we have known? Is this normal, do all secure elements have a door that can be accessed with simple firmware update. \n\nI personally thought that physical access was the only way to extract information from the secure element.",
"sig": "214d87666580ed90213259355a60b4e42d624c7b882cdb808eecc8bc5ed0034c532f5800a6e0ab5224e53870aa4c36c6dcf4385e3f990aab14c0158124f3ef2e"
}