-
Notifications
You must be signed in to change notification settings - Fork 62
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
Picopass nr mac improvements #108
Picopass nr mac improvements #108
Conversation
Note the config block can always be read so using that as a sentinel for "did we succeed to read a secured chip" may not work. The more I think about it the more storing flags for which blocks were successfully read makes sense, or at least a flag for "successfully read AA1" and "successfully read AA2" (speaking of we should really rename AA1 in the structure to just data since AA1 only starts after the AIA technically) Edit: and a flag for if we have each key |
This is checking the pacs config though, the first block of AA1 (right??)
Yeah, this was initially written before we'd talked about things and was supposed to be a simple clean up. I do think a bit-vector of read-blocks and/or auth method or known keys would be better and the direction we should go.
oh god, yeah |
oh herp, I misread that as the picopass config block not the PACS config block, nevermind |
This is ready for review: I can't review it since I opened it |
I'll merge it later today |
What's new
Verification
Checklist (For Reviewer)