Proxmark3 community

iceman

Administrator

Registered: 2013-04-25

Posts: 9,538

Website

[resolved] iceman fork is on hold - is up and running

With all improvements coming out from the execellent maintainers @piwi @marshmellow42 which brings very big changes to PM3 Master I have decided to keep iceman fork on hold until they have finished with their plans.  And yes, as seen from latest PR from marshmellow there is some nice and great improvements to the graphical interface for the proxmark client.  The whole demodulating of a LF signal will be enhanced. His posts on github shows very important new features.  Gone is the days when you have to look at a raw signal and understand how to decode it to a zero / one.   

This easyness will be good and bad. New ppl will buy a proxmark3 and have very little "deep" understanding of what is going on.  I share Marshmellows doubts, instead of learning ppl will click on a button and not know what is happening.

The work with merging all new ideas in PM3 master into iceman fork will take some time. I wish it will come to a point where I actually can start pushing back some of iceman fork changes into PM3 master. As you all know its been done only when @marshmellow got the time to do it. Its a slow process. Iceman fork will still be bleeding edge and PM3 master will be a great stable firmware as we have tried to uphold over all years.

Once the current changes is done, PM3 master will get a new "higher" version number (like v3.0) so we can get away from all confusing versioning of pre-compiled binaries (@asper, @iceman). 

Remember that I always wanted to get the most out of my proxmark3 device, thats why iceman fork is what it is.  It was never a way of undermining PM3 Master.  Just wanted to clarify that.  I have some interesting new device only functionality coming up but that has to wait until I can merge all goodies from @Piwi and @Marshmellow42.

I do love how much better the proxmark3 has become because of the endless selfless efforts of the main contributors. No one named, no one forgotten.  I know who you are.

My suggestion is to always try both PM3 master and iceman fork.  If it doesnt work in one,  it might be better in the other (or worse) but trust me, all svn versions (700,600,400 etc) is not even similary to what we got today.

When the PM3 master gets stable from all changes, I so look forward for piwi's work but that is a later story.

To round up, for now, iceman fork is on hold.

iceman

Administrator

Registered: 2013-04-25

Posts: 9,538

Website

Re: [resolved] iceman fork is on hold - is up and running

... and months later I have merged all changes.    I call it monster merge in my commits. Don't look at them to get any kind of idea what has been done.  Endless days of comparing source code from several branches/forks. 

I'm pretty sure I broke most of stuff.  Its untested in that sense.   The coverity scan is working as I write this post.

I also notice more client crashes in the client with the new gui - thingys.   I guess there is some out-of-bounds checks needed before applying the functionality to the lf signal is the cause.

So why write this if I'm not gonna write what has changed?
Its because I want you to be aware of this before you compile/flash iceman fork as of now.

iceman

Administrator

Registered: 2013-04-25

Posts: 9,538

Website

Re: [resolved] iceman fork is on hold - is up and running

Just to give people heads up,  iceman fork is very unstable at the moment. 

Use offical PM3 latest source,  to enjoy your proxmark3 experience to the fullest.