-
Notifications
You must be signed in to change notification settings - Fork 227
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
Diff Nt = 1 , The attack didn't progress... #64
Comments
I have the same with a single tag. Even if I know the keyA/B the dark-side attack doesn't work. |
Same Issue with PN532 via libnfc 1.7.1 and mfcuk 0.3.8+git20180720-1 even on test card which I bought with reader?! |
same problem |
Any ideas, what it could be? May be thus us this a new generation of cards,
cause we have this problem on older Lib versions too?
ср, 23 окт. 2019 г., 12:39 Jesus Victorio <[email protected]>:
… same problem
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#64?email_source=notifications&email_token=AB5UXU6PGXUISE3MHFG6HH3QQALVNA5CNFSM4F6IBMD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECAYP2Y#issuecomment-545359851>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5UXU2ZNQAP3XZPNJE2UX3QQALVNANCNFSM4F6IBMDQ>
.
|
I have the same problem. I also tried older lib versions without success. However! I know it worked with the exact same hardware (and even same attacked card) a few years ago. My guess then would be either dependencies of libnfc (like libusb e.g.) or changes in the linux kernel are to blame? |
Hi all !
I install lib 1.5.1 and mfcuk r65 with this link (https://gist.github.com/ceres-c/b84935799f5d65a4e41328d3ceaa075c)
my pcscd is ok , the communication was good (see screen)
but the differents Nt stay on 1 , and after 12hours its same... I dont understand why !
Anyone have this problem ? Thanks !
![capture du 2018-10-20 18-20-28](https://user-images.githubusercontent.com/25672488/47258070-35f17680-d496-11e8-8122-576e64a52727.png)
The text was updated successfully, but these errors were encountered: