update break mfoc and mfcuk

**Lancha** · 2013-06-06

when make the upgrade and break the mfoc and mfcuk say sh: 1: mfcuk: not found the same thing to mfoc i try remove and install again but i have the same error
how i fix it

**zimmaro** · 2013-06-07

Originally Posted by Lancha

when make the upgrade and break the mfoc and mfcuk say sh: 1: mfcuk: not found the same thing to mfoc i try remove and install again but i have the same error
how i fix it

hi

try this for return to old packages!! & not upgrade!
root@hk3r:~# cd /var/cache/apt/archives/

root@hk3r:/var/cache/apt/archives# dpkg -i mfoc_0.10.5-0kali0_i386.deb
dpkg: attenzione: retrocessione di mfoc dalla versione 0.10.5+0~git1370583818.fa47ca-1 alla 0.10.5-0kali0
(Lettura del database... 248517 file e directory attualmente installati.)
Preparativi per sostituire mfoc v.0.10.5+0~git1370583818.fa47ca-1 (utilizzando mfoc_0.10.5-0kali0_i386.deb)...
Estrazione del sostituto di mfoc...
Configurazione di mfoc (0.10.5-0kali0)...
Elaborazione dei trigger per man-db...

root@hk3r:/var/cache/apt/archives# dpkg -i mfcuk_0.3.7-0kali1_i386.deb
dpkg: attenzione: retrocessione di mfcuk dalla versione 0.3.7+0~svn91+ts1365772928-1 alla 0.3.7-0kali1
(Lettura del database... 248518 file e directory attualmente installati.)
Preparativi per sostituire mfcuk v.0.3.7+0~svn91+ts1365772928-1 (utilizzando mfcuk_0.3.7-0kali1_i386.deb)...
Estrazione del sostituto di mfcuk...
Configurazione di mfcuk (0.3.7-0kali1)...

root@hk3r:~# mfcuk -h

mfcuk - 0.3.7
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'
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_classic_tag type dump
-I mifare_ext.dmp - load input extended dump specific to this tool, has several more fields on top of mifare_classic_tag type dump
-o mifare.dmp - output the resulting mifare_classic_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 - milliseconds to sleep for SLEEP_AT_FIELD_OFF (Default: 10 ms)
-S - milliseconds to sleep for SLEEP_AFTER_FIELD_ON (Default: 50 ms)
-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
-v verbose_level - verbose level (default is O)

Usage examples:
Recove all keys from all sectors:
mfcuk -C -R -1
Recove the sector #0 key with 250 ms for all delays (delays could give more results):
mfcuk -C -R 0 -s 250 -S 250

root@hk3r:~# mfoc -h
Usage: mfoc [-h] [-k key]... [-P probnum] [-T tolerance] [-O output]

h print this help and exit
k try the specified key in addition to the default keys
P number of probes per sector, instead of default of 20
T nonce tolerance half-range, instead of default of 20
(i.e., 40 for the total range, in both directions)
O file in which the card contents will be written (REQUIRED)

Example: mfoc -O mycard.mfd
Example: mfoc -k ffffeeeedddd -O mycard.mfd
Example: mfoc -P 50 -T 30 -O mycard.mfd

This is mfoc version 0.10.5.
For more information, run: 'man mfoc'.

**zimmaro** · 2013-06-10

if in your kali worked! For not upgrade these packages in the future

on your-risk)

root@hk3r:~# echo mfcuk hold | dpkg --set-selections
root@hk3r:~# echo mfoc hold | dpkg --set-selections
root@hk3r:~# apt-get dist-upgrade
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Calcolo dell'aggiornamento... Eseguito
I seguenti pacchetti sono stati mantenuti alla versione attuale:
dsniff gpsd mfcuk mfoc
0 aggiornati, 0 installati, 0 da rimuovere e 4 non aggiornati.

**Lancha** · 2013-06-22

i upgrade my mfoc and mfcuk by Bleeding Edge Repos
when i try used this commands i have this error
dpkg: erro ao processar mfcuk_0.3.7-0kali1_i386.deb (--install):
não pode aceder ao arquivo: No such file or directory
Foram encontrados erros enquanto processava:
mfcuk_0.3.7-0kali1_i386.deb
say rhis file or directory dont exist
do i have to make download and install manualy

**g0tmi1k** · 2013-07-24

This is a result of using the bleeding edge and updating the tools.

If you have a need for bleeding edge repositories, you can add the following entry. Do not add this repo “for the heck of it” – it’s called “bleeding edge” for a reason. Packages in this repository are NOT manually maintained (they are auto-generated), and are low priority in general.

Source: http://docs.kali.org/general-use/kal...t-repositories

**zimmaro** · 2013-07-24

Originally Posted by g0tmi1k

This is a result of using the bleeding edge and updating the tools.

Source: http://docs.kali.org/general-use/kal...t-repositories

hi g0tm1lk! my respect!!

one little question (with your permission):
in my kaly-machines(fully-update) i've enable bleeding-edge repos but for example after update & upgrade (mfoc & mfcuk) (upgrade via repository) the ""new-versions" of tools not work!)
then I decided to stop INTO default version
thanks in advanced
http://imageshack.us/f/818/59l.png/

**g0tmi1k** · 2013-07-24

Originally Posted by zimmaro

hi g0tm1lk! my respect!!

one little question (with your permission):
in my kaly-machines(fully-update) i've enable bleeding-edge repos but for example after update & upgrade (mfoc & mfcuk) (upgrade via repository) the ""new-versions" of tools not work!)
then I decided to stop INTO default version
thanks in advanced
http://imageshack.us/f/818/59l.png/

Sorry, I don't understand your question - and your picture is a very small resolution (so I can't read/understand that too!)

**zimmaro** · 2013-07-24

Originally Posted by g0tmi1k

Sorry, I don't understand your question - and your picture is a very small resolution (so I can't read/understand that too!)

Sorry but the size to upload is 1600x1200 to press zoom function
The problem is : after update & upgrade mfoc & mfcuk don't work in my kali
Thx bye

**Lancha** · 2013-07-28

how i solve the problem my mfoc and mfcuk is broken to
how i repair this problem

**g0tmi1k** · 2013-07-29

This is what I did.
By removing bleeding edge - you'll stop it from updating back to newer version (which is broken)

Code:

root@kali ~$ vim /etc/apt/sources.list
root@kali ~$ tail /etc/apt/sources.list

deb http://http.kali.org/kali kali main non-free contrib
deb-src http://http.kali.org/kali kali main non-free contrib

## Security updates
deb http://security.kali.org/kali-security kali/updates main contrib non-free


## Bleeding edge
#deb http://repo.kali.org/kali kali-bleeding-edge main
root@kali ~$ apt-get update
Get:1 http://security.kali.org kali/updates Release.gpg [836 B]
Hit http://http.kali.org kali Release.gpg
Get:2 http://security.kali.org kali/updates Release [10.9 kB]
Hit http://http.kali.org kali Release
Get:3 http://security.kali.org kali/updates/main i386 Packages [103 kB]
Hit http://http.kali.org kali/main Sources
Hit http://security.kali.org kali/updates/contrib i386 Packages
Hit http://http.kali.org kali/non-free Sources
Hit http://security.kali.org kali/updates/non-free i386 Packages
Hit http://http.kali.org kali/contrib Sources
Hit http://http.kali.org kali/main i386 Packages
Hit http://http.kali.org kali/non-free i386 Packages
Hit http://http.kali.org kali/contrib i386 Packages
Ign http://security.kali.org kali/updates/contrib Translation-en_GB
Ign http://security.kali.org kali/updates/contrib Translation-en
Ign http://security.kali.org kali/updates/main Translation-en_GB
Ign http://security.kali.org kali/updates/main Translation-en
Ign http://security.kali.org kali/updates/non-free Translation-en_GB
Ign http://security.kali.org kali/updates/non-free Translation-en
Ign http://http.kali.org kali/contrib Translation-en_GB
Ign http://http.kali.org kali/contrib Translation-en
Ign http://http.kali.org kali/main Translation-en_GB
Ign http://http.kali.org kali/main Translation-en
Ign http://http.kali.org kali/non-free Translation-en_GB
Ign http://http.kali.org kali/non-free Translation-en
Fetched 114 kB in 7s (16.3 kB/s)
Reading package lists... Done
root@kali ~$ apt-cache showpkg mfcuk
Package: mfcuk
Versions: 
0.3.7+0~svn93+ts1371102184-1 (/var/lib/dpkg/status)
 Description Language: 
                 File: /var/lib/apt/lists/http.kali.org_kali_dists_kali_main_binary-i386_Packages
                  MD5: c5a6a25bd86fa6eafcd9ae6dc9f4f571

0.3.7-0kali1 (/var/lib/apt/lists/http.kali.org_kali_dists_kali_main_binary-i386_Packages)
 Description Language: 
                 File: /var/lib/apt/lists/http.kali.org_kali_dists_kali_main_binary-i386_Packages
                  MD5: c5a6a25bd86fa6eafcd9ae6dc9f4f571


Reverse Depends: 
  kali-linux,mfcuk
Dependencies: 
0.3.7+0~svn93+ts1371102184-1 - 
0.3.7-0kali1 - libc6 (2 2.1) libnfc4 (2 1.7.0~rc6-0) libusb-0.1-4 (2 2:0.1.12) 
Provides: 
0.3.7+0~svn93+ts1371102184-1 - 
0.3.7-0kali1 - 
Reverse Provides: 
root@kali ~$ apt-get install mfcuk
Reading package lists... Done
Building dependency tree       
Reading state information... Done
mfcuk is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
root@kali ~$ apt-get install mfcuk=0.3.7-0kali1
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be DOWNGRADED:
  mfcuk
0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 9 not upgraded.
Need to get 24.4 kB of archives.
After this operation, 43.0 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://http.kali.org/kali/ kali/main mfcuk i386 0.3.7-0kali1 [24.4 kB]
Fetched 24.4 kB in 0s (25.9 kB/s)
dpkg: warning: downgrading mfcuk from 0.3.7+0~svn93+ts1371102184-1 to 0.3.7-0kali1
(Reading database ... 308274 files and directories currently installed.)
Preparing to replace mfcuk 0.3.7+0~svn93+ts1371102184-1 (using .../mfcuk_0.3.7-0kali1_i386.deb) ...
Unpacking replacement mfcuk ...
Setting up mfcuk (0.3.7-0kali1) ...
root@kali ~$ mfcuk

mfcuk - 0.3.7
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_classic_tag type dump
-I mifare_ext.dmp - load input extended dump specific to this tool, has several more fields on top of mifare_classic_tag type dump
-o mifare.dmp - output the resulting mifare_classic_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 - milliseconds to sleep for SLEEP_AT_FIELD_OFF (Default: 10 ms)
-S - milliseconds to sleep for SLEEP_AFTER_FIELD_ON (Default: 50 ms)
-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:0x4888964f 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
-v verbose_level - verbose level (default is O)

Usage examples:
  Recove all keys from all sectors:
    mfcuk -C -R -1
  Recove the sector #0 key with 250 ms for all delays (delays could give more results): 
    mfcuk -C -R 0 -s 250 -S 250
root@kali ~$

**Lancha** · 2013-11-11

i have this error when execute the mfcuk and mfoc
mfcuk: error while loading shared libraries: libnfc.so.4: cannot open shared object file: No such file or directory
mfoc: error while loading shared libraries: libnfc.so.4: cannot open shared object file: No such file or directory

**zimmaro** · 2013-11-12

Originally Posted by Lancha

i have this error when execute the mfcuk and mfoc
mfcuk: error while loading shared libraries: libnfc.so.4: cannot open shared object file: No such file or directory
mfoc: error while loading shared libraries: libnfc.so.4: cannot open shared object file: No such file or directory

hi

lancha
i THINK :
is related to updating libnfc4 done through bleeding-edge-repo (ENABLE)!
return & block the "original"package(1.7.0~rc7-0kali1)..if you want to continue to use bleeding-edge-repo & have mfoc,mfcuk working-fine

this is my blocked-pachage-worked-version:
root@kali:~# dpkg --list |grep -e mfoc -e mfcuk -e libnfc4
hi libnfc4:i386 1.7.0~rc7-0kali1 i386 Near Field Communication (NFC) library
hi mfcuk 0.3.8-0kali1 i386 MFCUK - MiFare Classic Universal toolKit
hi mfoc 0.10.6-0kali0 i386 MIFARE Classic offline cracker
root@kali:~#

**Lancha** · 2013-11-12

if update the mfoc and mfcuk via bleeding-edge-repo is gonna break our is have been fixit

**zimmaro** · 2013-11-12

Originally Posted by Lancha

if update the mfoc and mfcuk via bleeding-edge-repo is gonna break our is have been fixit

Libnfc4 is ""connected"" to mfoc & mfcuk
I don't have problem with my mfoc mfcuk libhfc4 !!!!

**Lancha** · 2013-11-12

i do you say but i have the same error how i fixit-it

**zimmaro** · 2013-11-12

Originally Posted by Lancha

i do you say but i have the same error how i fixit-it

RI-I-THINK:
the errors comes from here:
http://imageshack.us/f/7/bmip.png/
THE ""MY FIX"" come from here:
https://vimeo.com/79247125

PS: now are 12.30 PM in my country..i finished my work & goto sleep.... wait about a hour to watching my ""camrec"" is making from""" vimeo-time-control""
@luck && good night

**Lancha** · 2013-11-13

thanks works fine
but now i don´t have the nfc-list
when i try install the libnfc-bin i have this error
say the libnfc-bin depeding of libnfc4 >= 1.7.0~rc7+0~git1384235197.a1ef32-1
and have this error libnfc.driver.acr122_usb Unable to claim USB interface (Device or resource busy)
No NFC device found
i using the touchtag
how i solve this problem

**zimmaro** · 2013-11-13

Originally Posted by Lancha

thanks works fine
but now i don´t have the nfc-list
when i try install the libnfc-bin i have this error
say the libnfc-bin depeding of libnfc4 >= 1.7.0~rc7+0~git1384235197.a1ef32-1
and have this error libnfc.driver.acr122_usb Unable to claim USB interface (Device or resource busy)
No NFC device found
i using the touchtag
how i solve this problem

.............mmm...the """little-game" is the same"
steps 1 to 8
http://imageshack.us/f/109/6x2o.png/
steps >8
http://imageshack.us/f/855/wa3v.png/

@zoom 1600x1200

**Lancha** · 2013-11-13

how desbloque the actulizacion is block ?
i can install the mfoc and mfcuk becouse i need the libnfc4
i upgrade to 1.7.0 but don´t solve the problem
use the command nfc-scan-device
nfc-scan-device uses libnfc 1.7.0
acr122_usb:003:003
error libnfc.driver.acr122_usb PN532 didn't reply
when use the command nfc-list i have this
nfc-list uses libnfc 1.7.0
NFC device: / CCID USB Reader opened

how i fix the problem
i using touchtag

Thread: update break mfoc and mfcuk

Thread Tools

Search Thread

Display

update break mfoc and mfcuk

Similar Threads

[A request for a break]

kali 2 x64 would break if run "dpkg --add-architecture i386" and update?

mfoc - segfault

Posting Permissions