You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1. git clone https://code.google.com/p/libnfc/
2. autoreconf -vis
3. ./configure --with-driver=pn32_uart --enable-serial-autoprobe
4. make
5. make install
6. sudo ldconfig
1. svn checkout http://mfcuk.googlecode.com/svn/trunk/ mfcuk-read-only
2. autoreconf -vis
3. ./configure
4. make
5. src/mfcuk -C -R 0:A -s 250 -S 250 -v 3
after a long!!! time this is what i get
[code]
Let me entertain you!
uid: -xxxxxxx-
type: 18
key: 000000000000
block: 5b
diff Nt: 65535
auths: 65537
-----------------------------------------------------
-----------------------------------------------------
Let me entertain you!
uid: -xxxxxx-
type: 18
key: 000000000000
block: 5b
diff Nt: 65536
auths: 65538
-----------------------------------------------------
mfcuk_keyrecovery_darkside: ERROR: mfcuk_key_recovery_block() (error code=0x09)
[/code]
when compiling mfcuk i have a make warning;
[code]
mfcuk.c:248:17: warning: ‘mfcuk_verify_key_block’ defined but not used
[-Wunused-function]
static uint32_t mfcuk_verify_key_block(nfc_device *pnd, uint32_t uiUID, uint64_t ui64Key, mifare_key_type bKeyType, uint8_t bTagType, uint32_t uiBlock)
[/code]
this problem is here with versions 0.3.5-0.3.8
i can use the -V option with the -D and it will find the default key's
but for some reason the -R option will not work, even when i add a default key
with the -d option.
please help.....!!!
uname
Linux 3.10-2-amd64 #1 SMP Debian 3.10.7-1 (2013-08-17) x86_64 GNU/Linux
i am using the pn532_uart breakout board v1.6
Original issue reported on code.google.com by surffreg...@hotmail.com on 15 Sep 2013 at 5:08
The text was updated successfully, but these errors were encountered:
I am having the same problem.
at compile time the error appears.
mfcuk.c: 248:17: warning: 'mfcuk_verify_key_block' defined but not used
[-Wunused-function]
Original comment by dudu...@gmail.com on 3 Oct 2013 at 4:36
Original issue reported on code.google.com by
surffreg...@hotmail.com
on 15 Sep 2013 at 5:08The text was updated successfully, but these errors were encountered: