Resultados 1 al 20 de 23

Hacking RFID, rompiendo la seguridad de Mifare

Vista híbrida

Mensaje anterior Mensaje anterior   Próximo mensaje Próximo mensaje
  1. #1 Ayuda con la compilaciòn de mfcuk 
    Iniciado
    Fecha de ingreso
    Aug 2010
    Mensajes
    10
    Descargas
    0
    Uploads
    0
    Saludos!

    Yo uso ubuntu 9.04

    mi archivo /etc/ld.so.conf:
    ==============================
    gandalf@gandalf-laptop:~$ cat /etc/ld.so.conf
    include /etc/ld.so.conf.d/*.conf
    include /usr/lib
    include /u01/app/oracle/product/11.1.0/db_1/lib

    /root/fuck/libnfc/libnfc-read-only/libnfc
    /root/fuck/libnfc/libnfc-read-only/libnfc/.libs
    /usr/local/lib/

    ======================================

    Can you help me: I get the following error when compiling with
    gcc -o mfcuk_keyrecovery_darkside mfcuk_keyrecovery_darkside.c -I/root/fuck/libnfc/libnfc-read-only/include -I. -L/usr/local -L./bin/libnfc.lib -lnfc ./*.o

    àrbol de directrios:

    Niel de diectorio contenedor
    ================================================== =
    root@gandalf-laptop:~/fuck# ls -la
    total 72
    drwxr-xr-x 18 root root 4096 2010-08-28 16:04 .
    drwx------ 51 root root 4096 2010-08-28 18:04 ..
    drwxr-xr-x 3 root root 4096 2010-08-27 22:42 02
    drwxr-xr-x 3 root root 4096 2010-08-28 18:03 03
    drwxr-xr-x 3 root root 4096 2010-08-28 10:11 04
    drwxr-xr-x 5 root root 4096 2010-08-28 16:28 7
    drwxr-xr-x 3 root root 4096 2010-08-28 13:20 crapto1
    drwxr-xr-x 3 root root 4096 2010-08-27 23:43 craptogui
    drwxr-xr-x 4 root root 4096 2010-08-27 13:44 driverlector
    drwxr-xr-x 3 root root 4096 2010-08-27 15:36 fuck
    drwxr-xr-x 3 root root 4096 2010-08-27 17:06 libnfc
    drwxr-xr-x 3 root root 4096 2010-08-27 13:15 libnfc-read-onlyautoreconf
    drwxr-xr-x 3 root root 4096 2010-08-28 08:49 librfid
    drwxr-xr-x 3 root root 4096 2010-08-27 17:17 mfcuk
    drwxr-xr-x 3 root root 4096 2010-08-28 11:09 mfoc
    drwxr-xr-x 3 root root 4096 2010-08-28 11:11 mfoc_new
    drwxr-xr-x 3 root root 4096 2010-08-27 23:29 rfdump
    drwxr-xr-x 3 root root 4096 2010-08-27 23:02 rfidiot


    Primer nivel:
    ================================================== =
    root@gandalf-laptop:~/fuck/03# ls -la
    total 136
    drwxr-xr-x 3 root root 4096 2010-08-28 18:03 .
    drwxr-xr-x 18 root root 4096 2010-08-28 16:04 ..
    -rwxr-xr-x 1 root root 18329 2010-08-28 17:06 cm
    -rw-r--r-- 1 root root 2814 2010-06-04 15:18 cm.c
    -rw-r--r-- 1 root root 8699 2010-06-04 15:17 crf.c
    -rw-r--r-- 1 root root 9402 2010-06-04 15:18 cryptolib.c
    -rw-r--r-- 1 root root 2036 2010-06-04 15:18 cryptolib.h
    -rw-r--r-- 1 root root 9324 2010-08-28 17:06 cryptolib.o
    -rw-r--r-- 1 root root 12329 2010-08-28 17:06 cryptomemrf.zip
    -rw-r--r-- 1 root root 1101 2010-06-04 15:24 defines.h
    -rw-r--r-- 1 root root 351 2010-05-07 07:17 Makefile
    drwxr-xr-x 5 root root 4096 2010-08-28 09:37 mfcuk-read-only
    -rwxr-xr-x 1 root root 18329 2010-08-28 17:06 sm
    -rw-r--r-- 1 root root 2372 2010-06-04 15:18 sm.c
    -rw-r--r-- 1 root root 1225 2010-06-04 15:24 util.c
    -rw-r--r-- 1 root root 1034 2010-06-04 15:24 util.h
    -rw-r--r-- 1 root root 1096 2010-08-28 17:06 util.o

    Segundo nivel:
    ================================================== ===

    root@gandalf-laptop:~/fuck/03/mfcuk-read-only/src# ls -l
    total 220
    drwxr-xr-x 4 root root 4096 2010-08-28 17:52 bin
    -rw-r--r-- 1 root root 334 2010-08-28 09:37 build_cygwin.sh
    -rw-r--r-- 1 root root 14007 2010-08-28 09:37 crapto1.c
    -rw-r--r-- 1 root root 3090 2010-08-28 09:37 crapto1.h
    -rw-r--r-- 1 root root 8332 2010-08-28 13:30 crapto1.o
    -rw-r--r-- 1 root root 2481 2010-08-28 09:37 crypto1.c
    -rw-r--r-- 1 root root 2096 2010-08-28 13:30 crypto1.o
    -rw-r--r-- 1 root root 321 2010-08-28 09:37 Makefile.am
    -rw-r--r-- 1 root root 5781 2010-08-28 09:37 mfcuk_finger.c
    -rw-r--r-- 1 root root 2186 2010-08-28 09:37 mfcuk_finger.h
    -rw-r--r-- 1 root root 3676 2010-08-28 13:30 mfcuk_finger.o
    -rw-r--r-- 1 root root 74442 2010-08-28 12:57 mfcuk_keyrecovery_darkside.c
    -rw-r--r-- 1 root root 6653 2010-08-28 09:37 mfcuk_keyrecovery_darkside.h
    -rw-r--r-- 1 root root 15747 2010-08-28 09:37 mfcuk_mifare.c
    -rw-r--r-- 1 root root 6995 2010-08-28 12:58 mfcuk_mifare.h
    -rw-r--r-- 1 root root 6324 2010-08-28 13:31 mfcuk_mifare.o
    -rw-r--r-- 1 root root 2377 2010-08-28 09:37 mfcuk_utils.c
    -rw-r--r-- 1 root root 3198 2010-08-28 09:37 mfcuk_utils.h
    -rw-r--r-- 1 root root 873 2010-08-28 13:32 mfcuk_utils.o
    -rw-r--r-- 1 root root 1412 2010-08-28 11:35 mifaretag.h
    -rw-r--r-- 1 root root 7083 2010-08-28 09:37 xgetopt.c
    -rw-r--r-- 1 root root 655 2010-08-28 09:37 xgetopt.h
    -rw-r--r-- 1 root root 1740 2010-08-28 13:32 xgetopt.o
    root@gandalf-laptop:~/fuck/03/mfcuk-read-only/src#

    aquì, compilando con:

    gcc -o mfcuk_keyrecovery_darkside mfcuk_keyrecovery_darkside.c -I/root/fuck/libnfc/libnfc-read-only/include -I. -L/usr/local -L./bin/libnfc.lib -lnfc ./*.o



    Obtengo el sig error:


    root@gandalf-laptop:~/fuck/03/mfcuk-read-only/src# gcc -o mfcuk_keyrecovery_darkside mfcuk_keyrecovery_darkside.c -I/root/fuck/libnfc/libnfc-read-only/include -I. -L/usr/local -L./bin/libnfc.lib -lnfc ./*.o
    mfcuk_keyrecovery_darkside.c: En la función ‘main’:
    mfcuk_keyrecovery_darkside.c:893: aviso: la constante entera es demasiado grande para el tipo ‘long’
    /tmp/ccgG1DnL.o: In function `mfcuk_verify_key_block':
    mfcuk_keyrecovery_darkside.c.text+0x2dc): undefined reference to `swap_endian32'
    mfcuk_keyrecovery_darkside.c.text+0x3c4): undefined reference to `oddparity'
    mfcuk_keyrecovery_darkside.c.text+0x499): undefined reference to `oddparity'
    /tmp/ccgG1DnL.o: In function `mfcuk_key_recovery_block':
    mfcuk_keyrecovery_darkside.c.text+0x8c8): undefined reference to `swap_endian32'
    mfcuk_keyrecovery_darkside.c.text+0xb86): undefined reference to `oddparity'
    mfcuk_keyrecovery_darkside.c.text+0xd38): undefined reference to `oddparity'
    /tmp/ccgG1DnL.o: In function `mfcuk_darkside_select_tag':
    mfcuk_keyrecovery_darkside.c.text+0x1db4): undefined reference to `nfc_initiator_select_tag'
    /tmp/ccgG1DnL.o: In function `main':
    mfcuk_keyrecovery_darkside.c.text+0x2525): undefined reference to `swap_endian32'
    mfcuk_keyrecovery_darkside.c.text+0x33f0): undefined reference to `print_hex'
    mfcuk_keyrecovery_darkside.c.text+0x35b7): undefined reference to `swap_endian32'
    mfcuk_keyrecovery_darkside.c.text+0x3765): undefined reference to `swap_endian32'
    mfcuk_keyrecovery_darkside.c.text+0x37ac): undefined reference to `swap_endian32'
    mfcuk_keyrecovery_darkside.c.text+0x3ab2): undefined reference to `nfc_initiator_select_tag'
    mfcuk_keyrecovery_darkside.c.text+0x3b07): undefined reference to `nfc_initiator_mifare_cmd'

    con:

    gcc -o zv_mf_dark_side zv_mf_dark_side.c ./crapto1-v3.1/crapto1.c
    ./crapto1-v3.1/crypto1.c ./libnfc-v1.2.1/bin/libnfc.lib -lnfc
    -I./libnfc-v1.2.1/include -L./libnfc-v1.2.1/lib

    No Compila correctamente.

    por cierto el paquete no lo puedo configurar y construir con los comandos que muestras, o talves es otra distro, me puedes decir donde la consigo!?

    Gracias.
    Citar  
     

  2. #2  
    Iniciado
    Fecha de ingreso
    Jun 2006
    Mensajes
    27
    Descargas
    2
    Uploads
    0
    Puedes pegar el log que te aparece cuando ejecutas ./autogen.sh y ./configure?.

    Ahora no recuerdo que version de ubuntu tengo instalada; ya lo mirare si quieres, pero no creo que vayan por ahi los tiros. Lo mas probable es que no tengas bien el entorno de compilacion o te falte algun paquete.

    Saludos.
    Citar  
     

  3. #3  
    Iniciado
    Fecha de ingreso
    Aug 2010
    Mensajes
    10
    Descargas
    0
    Uploads
    0
    Que tal izai!

    Creo que ese es precisamente el asunto, la version del software que yo baje de

    http://code.google.com/p/mfcuk/source/checkout

    descargado con:

    svn checkout http://mfcuk.googlecode.com/svn/trunk/ mfcuk-read-only


    no veo el archivo keygen ni el configure que mencionan.

    agradecere el apoyo, ¿Còmo genero esos archivos?¿Es otra distro de la que estan hablado? en tal caso de donde la descargo

    gracias de antemano
    Citar  
     

  4. #4 sobre autoconf en libnfc-read-only y en mfcuk-read-only 
    Iniciado
    Fecha de ingreso
    Aug 2010
    Mensajes
    10
    Descargas
    0
    Uploads
    0
    Os platico, después de descargar los directorios:

    %svn checkout http://mfcuk.googlecode.com/svn/trunk/ mfcuk-read-only
    %svn checkout http://libnfc.googlecode.com/svn/trunk/ libnfc-read-only
    y el tar-gz de crapto, tengo lo siguiente:

    ===============================================
    root@gandalf-laptop:~/fuck/8# ls -la
    total 20
    drwxr-xr-x 5 root root 4096 2010-08-31 15:50 .
    drwxr-xr-x 19 root root 4096 2010-08-31 14:45 ..
    drwxr-xr-x 3 root root 4096 2010-08-31 14:49 crapto
    drwxr-xr-x 12 root root 4096 2010-08-31 15:50 libnfc-read-only
    drwxr-xr-x 6 root root 4096 2010-08-31 15:48 mfcuk-read-only
    ===============================================
    root@gandalf-laptop:~/fuck/8# cd libnfc-read-only/

    root@gandalf-laptop:~/fuck/8/libnfc-read-only# ls

    AUTHORS cmake_modules configure.ac debian include LICENSE make_release.sh pn53x.rules windows
    ChangeLog CMake-Windows.txt contrib Doxyfile.in libnfc m4 NEWS README
    CMakeLists.txt config.h.cmake COPYING examples libnfc.pc.in Makefile.am pn53x.conf test

    root@gandalf-laptop:~/fuck/8/libnfc-read-only# ./make_release.sh

    >>> Cleaning sources...
    configure.ac:24: error: possibly undefined macro: AC_PROG_LIBTOOL
    If this token and others are legitimate, please use m4_pattern_allow.
    See the Autoconf documentation.
    autoreconf: /usr/local/bin/autoconf failed with exit status: 1
    <<< Sources cleaned.
    >>> Autotooled archive generation...
    configure.ac:24: error: possibly undefined macro: AC_PROG_LIBTOOL
    If this token and others are legitimate, please use m4_pattern_allow.
    See the Autoconf documentation.
    autoreconf: /usr/local/bin/autoconf failed with exit status: 1
    make: *** No hay ninguna regla para construir el objetivo `distclean'. Alto.


    y si tengo instalado libtool
    ==============================
    root@gandalf-laptop:~# libtool --version
    ltmain.sh (GNU libtool) 2.2.6
    Written by Gordon Matzigkeit <[email protected]>, 1996

    Copyright (C) 2008 Free Software Foundation, Inc.
    This is free software; see the source for copying conditions. There is NO
    warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.



    ::::::::::::::Referente a fcuk:::::::::

    root@gandalf-laptop:~/fuck/8# cd mfcuk-read-only/

    root@gandalf-laptop:~/fuck/8/mfcuk-read-only# ls

    aclocal.m4 autom4te.cache config.h.in configure COPYING INSTALL LICENSE Makefile.in NEWS src tools
    AUTHORS ChangeLog config.log configure.ac depcomp install-sh Makefile.am missing README TODO

    Esta bien que haga "autoconf" en este directorio... observo que se crea un archivo "configure"...
    root@gandalf-laptop:~/fuck/8/mfcuk-read-only# autoconf

    root@gandalf-laptop:~/fuck/8/mfcuk-read-only# ls -la

    total 416
    drwxr-xr-x 6 root root 4096 2010-08-31 15:48 .
    drwxr-xr-x 5 root root 4096 2010-08-31 15:50 ..
    -rw-r--r-- 1 root root 35537 2010-08-31 14:53 aclocal.m4
    -rw-r--r-- 1 root root 59 2010-08-31 14:46 AUTHORS
    drwxr-xr-x 2 root root 4096 2010-08-31 14:53 autom4te.cache
    -rw-r--r-- 1 root root 0 2010-08-31 14:46 ChangeLog
    -rw-r--r-- 1 root root 3771 2010-08-31 14:53 config.h.in
    -rw-r--r-- 1 root root 4665 2010-08-31 15:48 config.log
    -rwxr-xr-x 1 root root 196054 2010-08-31 14:53 configure
    -rw-r--r-- 1 root root 1797 2010-08-31 14:46 configure.ac
    -rw-r--r-- 1 root root 17987 2010-08-31 14:46 COPYING
    -rwxr-xr-x 1 root root 18615 2010-08-31 14:53 depcomp
    -rw-r--r-- 1 root root 15578 2010-08-31 14:53 INSTALL
    -rwxr-xr-x 1 root root 13663 2010-08-31 14:53 install-sh
    -rw-r--r-- 1 root root 17987 2010-08-31 14:46 LICENSE
    -rw-r--r-- 1 root root 79 2010-08-31 14:46 Makefile.am
    -rw-r--r-- 1 root root 21776 2010-08-31 14:53 Makefile.in
    -rwxr-xr-x 1 root root 11419 2010-08-31 14:53 missing
    -rw-r--r-- 1 root root 0 2010-08-31 14:46 NEWS
    -rw-r--r-- 1 root root 2259 2010-08-31 14:46 README
    drwxr-xr-x 4 root root 4096 2010-08-31 14:53 src
    drwxr-xr-x 6 root root 4096 2010-08-31 14:46 .svn
    -rw-r--r-- 1 root root 481 2010-08-31 14:46 TODO
    drwxr-xr-x 3 root root 4096 2010-08-31 14:46 tools

    root@gandalf-laptop:~/fuck/8/mfcuk-read-only#

    ::Sin embargo a la hora de ejecutarlo:::
    root@gandalf-laptop:~/fuck/8/mfcuk-read-only# ./configure
    checking for a BSD-compatible install... /usr/bin/install -c
    checking whether build environment is sane... yes
    checking for a thread-safe mkdir -p... /bin/mkdir -p
    checking for gawk... gawk
    checking whether make sets $(MAKE)... yes
    checking for pkg-config... /usr/bin/pkg-config
    ./configure: line 2816: syntax error near unexpected token `LIBNFC,'
    ./configure: line 2816: ` PKG_CHECK_MODULES(LIBNFC, libnfc, WITH_NFC=1, WITH_NFC=0)'

    ::or lo que infiero que primero se debe resolver el primer punto concerniente a libnfc:::

    Gracias por su ayuda.
    Citar  
     

  5. #5 Ando en esto... 
    Iniciado
    Fecha de ingreso
    Aug 2010
    Mensajes
    10
    Descargas
    0
    Uploads
    0
    Picandole he llegado a crear el archivo ejecutable de mfcuk_keyrecovery_darkside, espero haberlo creado bien -jejeje- si no ya andare posteandoles mi rrecorrido por este apasionante mundillo...


    solo que al ejecutarlo sale lo siguiente,,,,
    me podrian apoyar comentando la manera de usarlo, los parametros que se le pasan...

    ================================================== ==
    root@gandalf-laptop:~/fuck/9/libnfc/mfcuk-read-only# mfcuk_keyrecovery_darkside -h


    MFCUK - MiFare Classic Universal toolKit - 0.1
    Mifare Classic DarkSide Key Recovery Tool - 0.3
    by Andrei Costin, [email protected], http://andreicostin.com

    WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_skgt.mfd'
    WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_ratb.mfd'
    WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_oyster.mfd'
    Fallo de segmentación
    root@gandalf-laptop:~/fuck/9/libnfc/mfcuk-read-only#
    ================================================== =====
    si lo ejecuto sin parametros salen las opciones del programa

    root@gandalf-laptop:~/fuck/9/libnfc/mfcuk-read-only# mfcuk_keyrecovery_darkside

    MFCUK - MiFare Classic Universal toolKit - 0.1
    Mifare Classic DarkSide Key Recovery Tool - 0.3
    by Andrei Costin, [email protected], http://andreicostin.com


    Usage:
    -C - require explicit connection to the reader. Without this option, the connection is not made and recovery will not occur
    -i mifare.dmp - load input mifare_tag type dump
    -I mifare_ext.dmp - load input extended dump specific to this tool, has several more fields on top of mifare_tag type dump
    -o mifare.dmp - output the resulting mifare_tag dump to a given file
    -O mifare_ext.dmp - output the resulting extended dump to a given file
    -V sector[:A/B/any_other_alphanum[:fullkey]] - verify key for specified sector, -1 means all sectors
    After first semicolon key-type can specified: A verifies only keyA, B verifies only keyB, anything else verifies both keys
    After second semicolon full 12 hex-digits key can specified - this key will override any loaded dump key for the given sector(s) and key-type(s)
    -R sector[:A/B/any_other_alphanum] - recover key for sector, -1 means all sectors.
    After first semicolon key-type can specified: A recovers only keyA, B recovers only keyB, anything else recovers both keys
    -U UID - force specific UID. If a dump was loaded with -i, -U will overwrite the in the memory where dump was loaded
    -M tagtype - force specific tagtype. 8 is 1K, 24 is 4K, 32 is DESFire
    -D - for sectors and key-types marked for verification, in first place use default keys to verify (maybe you are lucky)
    -d key - specifies additional full 12 hex-digits default key to be checked. Multiple -d options can be used for more additional keys
    -s - miliseconds to sleep for DROP FIELD
    -S - miliseconds to sleep for CONSTANT DELAY
    -P hex_literals_separated - try to recover the key from a conversation sniffed with Proxmark3 (mifarecrack.c based). Accepts several options:
    Concatenated string in hex literal format of form uid:tag_chal:nr_enc:reader_resp:tag_resp
    Example -P 0x5c72325e:0x50829cd6:0xb8671f76:0xe00eefc9:0x4888 964f would find key FFFFFFFFFFFF
    -p proxmark3_full.log - tries to parse the log file on it's own (mifarecrack.py based), get the values for option -P and invoke it
    -F - tries to fingerprint the input dump (-i) against known cards' data format


    Gracias de antemano
    Citar  
     

  6. #6 Ayuda en el uso mfcuk con acr122u y mifare card? 
    Iniciado
    Fecha de ingreso
    Aug 2010
    Mensajes
    10
    Descargas
    0
    Uploads
    0
    Os comento:
    el trecer comando se queda colgado en error

    Hasta el momento he podido ejecutar los siguientes comandos y sus salidas respectivas:

    ================================================== ========
    1
    %mfcuk_keyrecovery_darkside -U 0240fe5d -M 8 -C 0

    MFCUK - MiFare Classic Universal toolKit - 0.1
    Mifare Classic DarkSide Key Recovery Tool - 0.3
    by Andrei Costin, [email protected], http://andreicostin.com


    INFO: Connected to NFC reader: ACS ACR122U 00 00 / ACR122U207 - PN532 v1.6 (0x07)


    VERIFY:
    Key A sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f
    Key B sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f

    RECOVER: 0 1 2 3 4 5 6 7 8 9 a b c d e f
    ================================================== ============
    La salida anterior me sugiere que esta trabajando de manera dummy sin hacer gran cosa...
    ================================================== ============


    2
    %mfcuk_keyrecovery_darkside -U 0240fe5d -M 8 -C 0 -V 1:A -o mifare_jhon.dmp

    MFCUK - MiFare Classic Universal toolKit - 0.1
    Mifare Classic DarkSide Key Recovery Tool - 0.3
    by Andrei Costin, [email protected], http://andreicostin.com


    INFO: Connected to NFC reader: ACS ACR122U 00 00 / ACR122U207 - PN532 v1.6 (0x07)


    VERIFY:
    Key A sectors: 0 1ERROR: AUTH sector 1, block 7, key 000000000000, key-type 0x60, error code 0x00
    2 3 4 5 6 7 8 9 a b c d e f
    Key B sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f

    RECOVER: 0 1 2 3 4 5 6 7 8 9 a b c d e f
    ================================================== ============

    3
    %mfcuk_keyrecovery_darkside -U 0240fe5d -M 8 -C 0 -R 1:A -o mifare_jhon.dmp

    MFCUK - MiFare Classic Universal toolKit - 0.1
    Mifare Classic DarkSide Key Recovery Tool - 0.3
    by Andrei Costin, [email protected], http://andreicostin.com


    INFO: Connected to NFC reader: ACS ACR122U 00 00 / ACR122U207 - PN532 v1.6 (0x07)


    VERIFY:
    Key A sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f
    Key B sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f

    RECOVER: 0 1

    ERROR: configuring NDO_ACTIVATE_FIELD
    ERROR: mfcuk_key_recovery_block() (error code=0x08)
    ERROR: configuring NDO_ACTIVATE_FIELD
    ERROR: mfcuk_key_recovery_block() (error code=0x08)
    ERROR: configuring NDO_ACTIVATE_FIELD
    ERROR: mfcuk_key_recovery_block() (error code=0x08)
    ERROR: configuring NDO_ACTIVATE_FIELD
    ERROR: mfcuk_key_recovery_block() (error code=0x08)
    ERROR: configuring NDO_ACTIVATE_FIELD
    ERROR: mfcuk_key_recovery_block() (error code=0x08)
    ERROR: configuring NDO_ACTIVATE_FIELD
    ERROR: mfcuk_key_recovery_block() (error code=0x08)
    ERROR: configuring NDO_ACTIVATE_FIELD
    ERROR: mfcuk_key_recovery_block() (error code=0x08)
    ERROR: configuring NDO_ACTIVATE_FIELD
    ERROR: mfcuk_key_recovery_block() (error code=0x08)
    ..
    ..
    ..
    ================================================== =============
    Se queda ciclado en ese error. Ademàs depuès de este comando el LED del lector se queda en rojo y ya no responde a otro comando... por lo cual cada vez que he ejecutado este comando he tenido que reiniciar el ordenador...
    ================================================== =============


    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
    Anexo la siguiente info de mi sistema-lector: Para que tengais más elementos al respecto y puedan auxiliarme...
    ================================================== =============
    root@gandalf-laptop:~# pcsc_scan
    PC/SC device scanner
    V 1.4.14 (c) 2001-2008, Ludovic Rousseau <[email protected]>
    Compiled with PC/SC lite version: 1.4.99
    Scanning present readers
    0: ACS ACR122U 00 00

    Sat Aug 28 14:12:40 2010
    Reader 0: ACS ACR122U 00 00
    Card state: Card inserted,
    ATR: 3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 01 00 00 00 00 6A

    ATR: 3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 01 00 00 00 00 6A
    + TS = 3B --> Direct Convention
    + T0 = 8F, Y(1): 1000, K: 15 (historical bytes)
    TD(1) = 80 --> Y(i+1) = 1000, Protocol T = 0
    -----
    TD(2) = 01 --> Y(i+1) = 0000, Protocol T = 1
    -----
    + Historical bytes: 80 4F 0C A0 00 00 03 06 03 00 01 00 00 00 00
    Category indicator byte: 80 (compact TLV data object)
    Tag: 4, len: F (initial access data)
    Initial access data: 0C A0 00 00 03 06 03 00 01 00 00 00 00
    + TCK = 6A (correct checksum)

    Possibly identified card (using /usr/share/pcsc/smartcard_list.txt):
    3B 8F 80 01 80 4F 0C A0 00 00 03 06 03 00 01 00 00 00 00 6A
    Philips MIFARE Standard (1 Kbytes EEPROM)
    http://www.nxp.com/products/identification/mifare/classic/
    RFID - ISO 14443 Type A - Transport for London Oyster

    ================================================== ==========
    root@gandalf-laptop:~# nfc-list
    nfc-list use libnfc 1.3.9 (r584)
    Connected to NFC reader: ACS ACR122U 00 00 / ACR122U207 - PN532 v1.6 (0x07)
    1 ISO14443A passive target(s) was found:
    ATQA (SENS_RES): 00 04
    UID (NFCID1): 5d fe 40 02 //Found MIFARE Classic 1k card with UID: 0240fe5d
    SAK (SEL_RES): 08

    0 Felica (212 kbps) passive target(s) was found.

    0 Felica (424 kbps) passive target(s) was found.

    0 ISO14443B passive target(s) was found.
    ================================================== ==============
    root@gandalf-laptop:~/fuck/9/libnfc/mfcuk-read-only/src/bin# nfc-anticol

    Connected to NFC reader: ACS ACR122U 00 00 / ACR122U207 - PN532 v1.6 (0x07)

    R: 26 (7 bits)
    T: 04 00
    R: 93 20
    T: 5d fe 40 02 e1
    R: 93 70 5d fe 40 02 e1 a2 ca
    T: 08 b6 dd
    R: 50 00 57 cd

    Found tag with UID: 5dfe4002
    ================================================== ==============
    root@gandalf-laptop:~# nfc-poll
    nfc-poll use libnfc 1.3.9 (r584)
    Connected to NFC reader: ACS ACR122U 00 00 / ACR122U207 - PN532 v1.6 (0x07)
    PN53x will poll during 6000 ms
    1 target(s) have been found.
    T1: targetType=10, targetData:
    ATQA (SENS_RES): 00 04
    UID (NFCID1): 5d fe 40 02
    SAK (SEL_RES): 08


    %%%%%%%%%%%%
    %%%%%%%%%%%%

    Gracias de antemano....
    Citar  
     

  7. #7  
    Iniciado
    Fecha de ingreso
    Jun 2006
    Mensajes
    27
    Descargas
    2
    Uploads
    0
    Me parece que tienes ahi un cacao de tres pares de cojones.

    Si no entiendo mal:

    root@gandalf-laptop:~/fuck/9/libnfc/mfcuk-read-only# mfcuk_keyrecovery_darkside

    Entiendo que tienes compilado el paquete mfcuk en la carpeta de la libreria nfc. La verdad es que no se como has conseguido hacer eso (bueno, si, me lo imagino). Son dos paquetes separados.

    Desinstala lo que tengas instalado.

    Instala primero el paquete libnfc y despues compilas mfcuk.

    Una vez lo tengas compilado, te situas en la carpeta src y lo ejecutas.

    El paquete parece que esta aqui:

    http://code.google.com/p/mfcuk/source/browse/trunk/src/?r=2

    Supongo que estara entero. No se.

    Saludos.
    Citar  
     

Temas similares

  1. E-Zine: Hacking & Seguridad
    Por NickBlack en el foro GENERAL
    Respuestas: 3
    Último mensaje: 13-08-2016, 09:14
  2. Congreso Seguridad y Hacking NoCONName 2014
    Por NoCONName en el foro NOTICIAS
    Respuestas: 5
    Último mensaje: 23-09-2014, 05:21
  3. Respuestas: 1
    Último mensaje: 17-11-2011, 22:56
  4. Mundo hacker tv ep.8 - seguridad y hacking web
    Por Yan125 en el foro HACK HiSPANO
    Respuestas: 3
    Último mensaje: 06-09-2011, 09:09
  5. Respuestas: 5
    Último mensaje: 14-11-2002, 19:42

Marcadores

Marcadores