Revise "full" recovery script #2706
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ot support (v1.4)
|
You are welcome to add an entry to the CHANGELOG.md as well |
|
Having a nice identification of tags is nice but it tends to become spaghetti code fast |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Revise 'RF08S_full' script to NOT attempt to recover a card it does not support (v1.4)
I tried to add support for other cards to it, but the code just isn't up to it.... Different block counts, variable sector sizes, bespoke code for certain blocks ...it would probably be prudent to abstract the KDF & decode functionality too.
I plan to develop a more structured approach that will present a more adaptable solution to the problem.
I now have a modest selection of card/chips/tags, so I need to start reading datasheets and work out what other quirks are hiding in the bushes - eg. I never anticipated variable sector sizes!