You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you try to reset the card with the wrong keys, you will get an 91AE error.
What many users try to do is try the same key again and again. Then they might try some other key again and again. Eventually they loose track of which cards they have tried, and I think this process eventually bricks the card.
If you want to reset the card, the card is already programmed and when read, the card will give off a c and a p value. These values can be decrypted with K1 to get the UID of the card.
Instead of trying to wipe the card, the user should first check if they have the right keys. If they check with the card, they get the 91AE error. If they try to decrypt the UID with K1 based on the c and p values read from the card, they can make sure they have the right key before wiping. This extra check could be done by this app just before wiping, and if the key is wrong, the user should get a warning that they are very likely trying to wipe the card with the wrong keys.
I implemented a simple proof of concept for this because I am looking through json files with keys to recover bolt cards and I am not quite sure which json file is for which card: https://amperstrand.github.io/boltcard-proxy/recover.html
The text was updated successfully, but these errors were encountered:
actually the above might not quite work: K1 is the issuer key, so it might be the same for many cards if the keys are derived in a deterministic way.
You would probably need one of the other keys too to check that they match the card.
But either way, it should be easy to first check that you are likely to have the correct key before trying to wipe the card. If you brute force against the card it will brick, but if you brute force on a computer first, you can figure out which key to use.
If you try to reset the card with the wrong keys, you will get an 91AE error.
What many users try to do is try the same key again and again. Then they might try some other key again and again. Eventually they loose track of which cards they have tried, and I think this process eventually bricks the card.
If you want to reset the card, the card is already programmed and when read, the card will give off a c and a p value. These values can be decrypted with K1 to get the UID of the card.
Instead of trying to wipe the card, the user should first check if they have the right keys. If they check with the card, they get the 91AE error. If they try to decrypt the UID with K1 based on the c and p values read from the card, they can make sure they have the right key before wiping. This extra check could be done by this app just before wiping, and if the key is wrong, the user should get a warning that they are very likely trying to wipe the card with the wrong keys.
I implemented a simple proof of concept for this because I am looking through json files with keys to recover bolt cards and I am not quite sure which json file is for which card: https://amperstrand.github.io/boltcard-proxy/recover.html
The text was updated successfully, but these errors were encountered: