-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NFC Ultralight C Unlock Manually Password Too Short #3668
Comments
Yes, it is a bit confusing. I wanted to unlock my tag with "BREAKMEIFYOUCAN!" key and saw only four bytes to fill in. |
@gornekich should we give @Astrrra this task? |
@skotopes yes. We need to add authentication for Ultralight C |
this task? |
@gornekich I can confirm I can type in the password and try unlocking the card with #3720 . However, since I didn't know the password of the card, and my guessed password was probably wrong, it just stucked in the "Don't move" page. I'm sure you have ULC cards on your end of which you know the correct password. There is a small caveat: when I typed in the wrong password in Unlock, and quit during "Don't move" page, try reading the card again without quitting the app, it was unable to read the card. It stucked at the "Don't move" page in Read. But after I quit the NFC app and reenter, Read works again. |
Describe the bug.
When an Mifare Ultralight C card is read and found to be password protected, there is the option to Unlock - Enter Password Manually. ULC's password is 16-byte long, but in this manually input interface, there are only 4 bytes allowed (see below).
There appears to be left and right arrows to the side of the password box, but pressing left or right button only allows one to select different bytes but not go to a next or a previous page.
I've also got suggestions from NFC Gandalf and NFC Samwise on Discord to ask for a new feature to have the default 3des key to be tried in the read procedure for ULC
Reproduction
Read a password protected ULC card, go to Unlock - Enter Password Manually. You will discover that it won't allow going to the next 4 bytes.
Target
No response
Logs
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: