Desfire commands started

morphine · 2015-12-22 11:51:24

Yes i have, I manage to compile it using the ubuntu cmd, "make UBUNTU_1404_QT4=1".

great fork!

morphine · 2015-12-22 11:53:42

Now i only need the bins for the peterfillmore fork..

iceman · 2015-12-22 12:03:45

U'll need to compile and flash with peterfillmore's fork if you wanna test his stuff.

You don't mix firmware images and client bins between forks/branches. That way leads to no good.

morphine · 2015-12-22 13:24:43

Yes i know, but i have two pm3 one for stable rls firmwares and one for testing forks etc.

No intension to mix like you wrote

edit: but i cant get peters fork to work, get only errors like i wrote..

Last edited by morphine (2015-12-22 13:26:47)

iceman · 2015-12-22 15:59:39

could be the makefile. try compare between pm3 master and his.

morphine · 2015-12-23 11:34:31

what i do with the makefile i only get this error:

[== Undefined ==]
gcc -std=c99 -I. -I../include -I../common -I../zlib -I/mingw/include -I/opt/local/include -I../liblua -Wall  -g -O4 -DHAVE_GUI -DZ_SOLO -DZ_PREFIX -DNO_GZIP -DZLIB_PM3_TUNED  -c -o obj/proxmark3.o proxmark3.c
In file included from proxmark3.h:16:0,
                 from proxmark3.c:20:
/usr/include/inttypes.h:290:8: error: unknown type name ‘intmax_t’
 extern intmax_t imaxabs (intmax_t __n) __THROW __attribute__ ((__const__));
        ^
/usr/include/inttypes.h:290:26: error: unknown type name ‘intmax_t’
 extern intmax_t imaxabs (intmax_t __n) __THROW __attribute__ ((__const__));
                          ^
/usr/include/inttypes.h:293:27: error: unknown type name ‘intmax_t’
 extern imaxdiv_t imaxdiv (intmax_t __numer, intmax_t __denom)
                           ^
/usr/include/inttypes.h:293:45: error: unknown type name ‘intmax_t’
 extern imaxdiv_t imaxdiv (intmax_t __numer, intmax_t __denom)
                                             ^
/usr/include/inttypes.h:297:8: error: unknown type name ‘intmax_t’
 extern intmax_t strtoimax (const char *__restrict __nptr,
        ^
/usr/include/inttypes.h:301:8: error: unknown type name ‘uintmax_t’
 extern uintmax_t strtoumax (const char *__restrict __nptr,
        ^
/usr/include/inttypes.h:305:8: error: unknown type name ‘intmax_t’
 extern intmax_t wcstoimax (const __gwchar_t *__restrict __nptr,
        ^
/usr/include/inttypes.h:310:8: error: unknown type name ‘uintmax_t’
 extern uintmax_t wcstoumax (const __gwchar_t *__restrict __nptr,
        ^
In file included from /usr/include/features.h:374:0,
                 from /usr/include/stdio.h:27,
                 from proxmark3.c:12:
/usr/include/inttypes.h:324:1: error: expected ‘,’ or ‘;’ before ‘strtoimax’
 __NTH (strtoimax (const char *__restrict nptr, char **__restrict endptr,
 ^
/usr/include/inttypes.h:336:1: error: expected ‘,’ or ‘;’ before ‘strtoumax’
 __NTH (strtoumax (const char *__restrict nptr, char **__restrict endptr,
 ^
/usr/include/inttypes.h:348:1: error: expected ‘,’ or ‘;’ before ‘wcstoimax’
 __NTH (wcstoimax (const __gwchar_t *__restrict nptr,
 ^
/usr/include/inttypes.h:362:1: error: expected ‘,’ or ‘;’ before ‘wcstoumax’
 __NTH (wcstoumax (const __gwchar_t *__restrict nptr,
 ^
In file included from uart.h:52:0,
                 from proxmark3.c:23:
/usr/include/x86_64-linux-gnu/sys/types.h:197:1: error: conflicting types for ‘int64_t’
 __intN_t (64, __DI__);
 ^
In file included from /usr/include/inttypes.h:27:0,
                 from proxmark3.h:16,
                 from proxmark3.c:20:
../include/stdint.h:17:25: note: previous declaration of ‘int64_t’ was here
 typedef long long int   int64_t;
                         ^
Makefile:181: receptet för målet ”obj/proxmark3.o” misslyckades

Do u mind try to compile it?

iceman · 2015-12-23 11:56:55

Are you talking about peterfillmore's fork? Why not ask him about it?
My dev env is the mingw, that wouldn't help you for the pm3 client. You would only get the firmware images

morphine · 2015-12-23 13:01:11

Yeah, i allready mailed him..

Ok, I see

FireFart · 2016-01-07 10:37:09

So will you create a pull request so your new command will be included in the official firmware?

iceman · 2016-02-08 08:16:30

Thanks to a forum user, I got my hands on a desfire tag with a default key. I can once again look into desfire commands.

TheJuice · 2016-04-21 16:10:02

iceman wrote:

Thanks to a forum user, I got my hands on a desfire tag with a default key. I can once again look into desfire commands.

Hi iceman,
I saw that you implemented more advanced desfire commands, so I downloaded your fork... But I cannot compile it.

Here's what I did : In my ProxSpace, I totally replaced the pm3 folder with your sources. I then executed the make command.
Here is the error I encountered :

gcc -std=c99 -O3 -mpopcnt -march=native -I. -I../include -I../common -I../zlib -I/opt/local/include -I../liblua -Wall -g -/mingw/include -DHAVE_GUI -DZ_SOLO -DZ_PREFIX -DNO_GZIP -DZLIB_PM3_TUNED  -c -o obj/nonce2key/crypto1_bs.o nonce2key/crypto1_bs.c
In file included from nonce2key/crypto1_bs.c:25:
nonce2key/crypto1_bs.h:25: error: alignment of array elements is greater than element size
make[1]: *** [obj/nonce2key/crypto1_bs.o] Error 1
make[1]: Leaving directory `/pm3/client'
make: *** [client/all] Error 2

The "normal" pm3 code compiles fine on my computer in Mingw32

Thanks in advance.

iceman · 2016-04-21 16:39:29

hm, open a issue on github and lets talk about it there.

iceman · 2016-04-22 08:51:28

see http://www.proxmark.org/forum/viewtopic … 093#p21093 about the error..

TheJuice · 2016-04-22 10:00:30

Hi,
I tried to open the github issue yesterday, but I just went to the webpage and it is nowhere to be seen.
I tried removing the "-march=native" in the client\makefile and still got the same error.
Also tried to replace it with: "-mmmx" or "-msse", but got the same error every time...

Do you still want me to open the issue on github ? (maybe I missed a final step to open it)

iceman · 2016-04-22 10:11:05

I noticed that "issues" wasn't enabled on the fork yesterday. I added it.
What are you compiling on? The other forum user didn't have a problem after removing the "-march=native" param.
I hope you compile with
"make clean && make all"...

TheJuice · 2016-04-22 10:19:46

Hi,
think I could open the issue this time : https://github.com/iceman1001/proxmark3/issues/5
thanks

tjhowse · 2016-06-02 01:25:09

Hi,

Can this fork, as it stands, emulate a Desfire EV1 AES card with blank keys, one application and one file? Looking at the source, it seems not, but I might have missed something.

Thanks,
tjhowse.

iceman · 2016-06-02 07:13:14

The short answer is no, it can't.

tjhowse · 2016-06-17 05:05:38

I bought a blank desfire card from ebay, and I also have some desfire cards with known keys. I have got your fork running in your well-documented docker image.

I've got your "hf mfdes info" command dumping lots of tasty info, but I'm not sure what I should be expecting out of "hf mfdes auth ...", "rdbl ..." and "wdbl ...". It looks like reading/writing application data doesn't exist yet, unless I'm misreading something?

Thanks,
tjhowse.

iceman · 2016-06-17 07:50:57

The desfire commands is unfinished, basicaly only the "info" command works. There is alot to be done.

dario · 2019-05-01 14:55:23

Hi, iceman. What's the solution for the authenticating issue? I have a similar problem and maybe your solution can help me. The nfc-tool's link is broken

dario · 2019-05-01 14:58:26

Sorry, I mean this link is broken
http://www.libnfc.org/community/topic/8 … r-desfire/

Proxmark3 community

Announcement

#51 2015-12-22 11:51:24

Re: Desfire commands started

#52 2015-12-22 11:53:42

Re: Desfire commands started

#53 2015-12-22 12:03:45

Re: Desfire commands started

#54 2015-12-22 13:24:43

Re: Desfire commands started

#55 2015-12-22 15:59:39

Re: Desfire commands started

#56 2015-12-23 11:34:31

Re: Desfire commands started

#57 2015-12-23 11:56:55

Re: Desfire commands started

#58 2015-12-23 13:01:11

Re: Desfire commands started

#59 2016-01-07 10:37:09

Re: Desfire commands started

#60 2016-02-08 08:16:30

Re: Desfire commands started

#61 2016-04-21 16:10:02

Re: Desfire commands started

#62 2016-04-21 16:39:29

Re: Desfire commands started

#63 2016-04-22 08:51:28

Re: Desfire commands started

#64 2016-04-22 10:00:30

Re: Desfire commands started

#65 2016-04-22 10:11:05

Re: Desfire commands started

#66 2016-04-22 10:19:46

Re: Desfire commands started

#67 2016-06-02 01:25:09

Re: Desfire commands started

#68 2016-06-02 07:13:14

Re: Desfire commands started

#69 2016-06-17 05:05:38

Re: Desfire commands started

#70 2016-06-17 07:50:57

Re: Desfire commands started

#71 2019-05-01 14:55:23

Re: Desfire commands started

#72 2019-05-01 14:58:26

Re: Desfire commands started

Board footer