-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Hitag2 Support #1534
Comments
If you are referring to cracking HiTag2 - it is computationally very expensive to crack - and certainly not in the (realistic) remit of a FZ. However, I don't see why you couldn't use a FZ to collect the data for offline attacks. |
@csBlueChip I don't know if HITAG 2 uses the same system as HITAG S but for me it would be enough if flipper would support reading the uid and other data in plain mode without auth and also emulate the uid. If I am rememeber correctly you need an extra IC for auth (Philips Co Processor HT RC130) which surely is not in the FZ. |
fyi, I recently finished my developments for an external app which can read & emulate the HITAG 1 cards. Since all hitag types are quite similar in nature (meaning they all work with bidirectional cmd & reply modes, vs most other onedirectional LFRFID tags) I believe I could also add support for HITAG 2 and S. EDIT I do plan to commit my code to the official firmware, though currently looking for advice on how to properly do so (keep it as external unofficial app and publish in the app catalog once that becomes available, or include it as official app in the firmware, or include it in the main LFRFID app) |
@daandewitte I have some hitag2 cards so if you send me the app I can have a crack with it and test it against hitag2 |
hi @gsp8181 , afraid it's not that simple :( I can give it a go and include the hitag 2 commands as well If I find some time to update, I'll send you the app file ;) |
Any news on this? I see the pr has become stale atm in terms of discussion. |
For as far as I understood the cracking/challenge response is a tough subject, but (from an outsider's perspective) it does look like normal password encoding is cleartext and you "just" need to know the password (and sniffing it is relatively easy as well since it's sent cleartext). So it does look like, even if there are limitations to rolling out Hitag2 support, there's some functionality that's relatively easy to implement. @blackvault88 while I lack the knowledge to help out with the code itself, I can offer help in terms of testing and debugging of the protocol, or even sourcing hardware that might help you. Feel free to reach out to me by email if I can help out. I'd love to see more support for Hitag in general! |
Description of the feature you're suggesting.
Would it be possible to support Hitag2 tags under the 125kHz RFID function?
I'm not sure if the code in this project would be of any help.
Anything else?
No response
The text was updated successfully, but these errors were encountered: