Proxmark developers community

Research, development and trades concerning the powerful Proxmark3 device.

Remember; sharing is caring. Bring something back to the community.


"Learn the tools of the trade the hard way." +Fravia

You are not logged in.

#1 2017-09-06 18:46:23

magny
Contributor
Registered: 2017-09-06
Posts: 12

Brew installation question

Hi

I installed both the iceman and the official versions from homebrew, none of these versions installs the files from the client directory anywhere where I can find them. So embeded lua scripts dont exists and the default_keys.dic is not accessible from the brew installation.

Is there something I am missing?, I followed the instructions here:
https://github.com/iceman1001/proxmark3
and
https://github.com/Proxmark/homebrew-proxmark3

Best regards magny

Offline

#2 2017-09-06 19:00:21

iceman
Administrator
Registered: 2013-04-25
Posts: 3,876
Website

Re: Brew installation question

Not that I think it changes but homebrew for iceman fork is here: https://github.com/iceman1001/homebrew-proxmark3

Since I don't have access to mac/OSX I never could verify/test it properly but it should download the release zip.
Which contains it all.  Question is where it all gets installed... you would need to know about that when trying to run a lua script...


modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#3 2017-09-06 19:28:31

magny
Contributor
Registered: 2017-09-06
Posts: 12

Re: Brew installation question

yeah I see,

from iceman1001/homebrew-proxmark3/proxmark3.rb

#    system "make", "-C", "client/hid-flasher/"
    system "make", "clean"	  
    system "make", "all"
    bin.mkpath
    bin.install "client/flasher" => "proxmark3-flasher"
#    bin.install "client/hid-flasher/flasher" => "proxmark3-hid-flasher"
    bin.install "client/proxmark3" => "proxmark3"
    bin.install "client/fpga_compress" => "fpga_compress"
    share.mkpath
    (share/"firmware").mkpath
    (share/"firmware").install "armsrc/obj/fullimage.elf" => "fullimage.elf"
    (share/"firmware").install "bootrom/obj/bootrom.elf" => "bootrom.elf"
#    ohai "Install success! Upgrade devices on HID firmware with proxmark3-hid-flasher, or devices on more modern firmware with proxmark3-flasher."
	ohai "Install success!  Only proxmark3-flasher (modern firmware) is available."
    ohai "The latest bootloader and firmware binaries are ready and waiting in the current homebrew Cellar within share/firmware."

actually the only thing that is installed is 3 binaries shown above,

proxmark3-flasher
proxmark3
fpga_compress

and the firmwares to the share/firmware folder,
fullimage.elf
bootrom.elf

It could be quite easily fixed by adding everything else to the bin.install folder that needs to be relative to the proxmark3 binary.
I am bit new the proxmark source, so I dont know exactly what needs to be installed more from the client directory, noticed that the lua scripts and modules needed to be built and copied over, what more needs to be present to function properly?

Offline

#4 2017-09-06 19:36:47

iceman
Administrator
Registered: 2013-04-25
Posts: 3,876
Website

Re: Brew installation question

ok, where does this compilation occure then?

    system "make", "clean"	  
    system "make", "all"

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#5 2017-09-06 19:56:50

magny
Contributor
Registered: 2017-09-06
Posts: 12

Re: Brew installation question

https://docs.brew.sh/Formula-Cookbook.h … erminology

Its in a temporary folder that gets removed after installation is complete.

Offline

#6 2017-09-06 19:59:00

iceman
Administrator
Registered: 2013-04-25
Posts: 3,876
Website

Re: Brew installation question

ok.. because then we need to copy stuff from that temporay folder while it still exists smile

and where does it place the binaries?  Some suggestion for suitable folder location?


modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#7 2017-09-06 20:07:41

iceman
Administrator
Registered: 2013-04-25
Posts: 3,876
Website

Re: Brew installation question

and now I understand why hardnested doesnt work smile  haha..

the following folders needs to by copied!

  • client/hardnested

  • client/lualibs

  • client/scripts

  • traces

Additional files to be copied!

  • client/default_keys.dic

  • client/default_pwd.dic

And some extra tools like mfkey, should also be installed..


modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#8 2017-09-06 20:58:06

iceman
Administrator
Registered: 2013-04-25
Posts: 3,876
Website

Re: Brew installation question

I pushed a fix to iceman/homebrew  where I've address the need to copy some files into their right places. 
Now we just need to test it iron out the eventual problems.


modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#9 2017-09-06 20:58:34

magny
Contributor
Registered: 2017-09-06
Posts: 12

Re: Brew installation question

Lua/script support works by adding, (script list, lists all the scripts)

    bin.install "client/lualibs" => "lualibs"
    bin.install "client/scripts" => "scripts"

But I dont know how the other default_keys.dic and traces are referenced in the source. I copied it over but I dont think it reference the files relative to the proxmark3 binary. It feels a bit that you need to run proxmark3 from within the client folder to actually get everything to work correctly?

Offline

#10 2017-09-06 21:20:11

iceman
Administrator
Registered: 2013-04-25
Posts: 3,876
Website

Re: Brew installation question

Its usually recommended to run the client from the client-folder,  but a few months ago there was a fix which allows for takes account for the currentdir when running the client.   However running lua-scripts still assumes the existence of lualibs and scripts folder underneath the current folder. .. 
The hardnested folder I guess behavies the same.   So you will need those three folders definitly.

The traces folder is there if you want to load and watch how different LF tags looks like.  Use data load traces/xxxx.pm3 to load one trace which exists under the executing folder.    A bit confusing talking about which folder we talk about given the automatic nature of homebrew.

The default_*.dic files is the same with..     Or  "../default_keys.dic"  is one level above..    "/extrafolder/default_keys.dic"  is one below..


modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

Board footer

Powered by FluxBB