If we are talking achievable dreams, I personally wouldn’t be talking about a Proxmark.
I get the Linux:Linux relationship, but I would rather a, less bulky, more user friendly option.
However staying on that same thought path, and still engaging the achievable dream
INTERFACE
Rather than a terminal, how about an app to interface, using buttons for the common commands. One button push vs typing script.
HARDWARE
The RDV4 when spread out would be relatively low profile ( I wonder if a Proxmak including Antennas could be made on a flexible PCB ) and Re: the RDV4 having an exposed UART
Yeah, I thought about an RDV4, would be the better option by far, albeit a very very expensive one.
I mainly was focused on a proxmark, because I’m not aware of any LF breakout boards or chips that interface over I2C or serial, and also happen to be anywhere close to as flexible as the proxmark. An LF equivalent to the PN532 in terms of support & ease of use would be nice, but I don’t know of any. If anyone does, PLEASE let me know, I’m very interested in that.
Also damn, I meant headphone jack, not USB port. Fixed in an edit. Guess that’s what happens when I try to type a long reply on 3 hours of sleep haha.
I feel like a python gui wouldn’t be too difficult but would only work if you already had pm3 installed. Getting an easy and graphical way to install the software would seem to be much more difficult.
I tried reimplementing a few PM3 client commands in Lua and in pure Python, and it gets tricky very quickly - as in, you’re looking at reimplementing the entire client essentially. There are several problems with that:
The PM3’s protocol is a hodgepodge of high-level commands that get executed by the PM3’s hardware (easy to implement) and low-level raw data reads and writes that are decoded and interpreted client-side (harder)
The documentation is beyond sketchy (read: there isn’t one - read the code)
It’s a shifting target: it keeps changing from one iteration of the firmware / client to the next, which is why it’s so important to keep the two in sync.
In the end, I decided the bext course of action is to use the client as a backend. Spawn it as a separate process, send it commands through its stdin and get the results back through its stdout. And even that is not ideal: for instance, SiRFIDaL can use the PM3 as a reader, but I’ve had one report telling me it doesn’t work anymore because either one of the commands it issues it has changed, or the client’s output has changed and the regex used to recover the data it needs doesn’t match anymore.
The PM3’s software - firmware and hardware - is a maintainability, interoperability and compatibility nightmare. If it wasn’t a community project that someone kindly does on his own time, I’d be extremely pissed off with it.
I’ve had success with running a Sonny PaSoRi via NFCPy from my Pine.
And it’s one that looks like it could be flattened down pretty nicely.
Just adding 2 cents, while it’s kinda hard for me to forum up this week =P
For a full on GUI, yes.
But all you actually need is to extend a terminal.
Add one row of buttons, manage the state of the application, and present buttons to the user based on what he is doing.
One button press = pipe a command to be executed in that terminal.
For a mobile integration that hybrid solution would cover all my GUI needs to be honest.
As in,…
If I am using a proxmark, either I am “setting up shop”
so I want a keyboard + mouse + terminal
Or I am doing a very selkect and pre-defined set of operations, such as read then clone.
in which case, I just need 3/4 buttons total, and the terminal output is there only to help me double check stuff
we kinda have that now… when shaking hands you use your thumb to probe around L0 for an implant in the person’s hand you’re shaking works pretty well actually.
It works well unless you can’t feel any implant. Then you’re left trying to explain to a random dude why you’ve been fondling his hand with your thumb for the last 5 seconds.
yeah… basically you shake their hand as normal with your right hand… then you grapple them to the ground and put their left arm in a leg lock… then jab your thumb into their hand repeatedly until you find a chip or the police arrive. simple really. works really well!
No no, it’s really subtle… normies don’t even notice their arm being pulled from its socket.
I’m thinking flex pcb layers for a seven segment display, a razor thin battery with a qi charger module, and probably some kind of specialized illuminating bit (don’t think smd LEDs will make the cut). Maybe OLED if power wasn’t an issue but idk.
I’ve hacked little things together over the years. I feel like this wouldn’t be too difficult to achieve. Using straight flex oled is still a long way off though, the tech just isn’t there yet. If I or someone could think of an ingenious way to get the lumins needed on such a display then the only thing left would be to figure how to implant that monster without too much scarring
) and Re: the RDV4 having an exposed UART
works pretty well actually.
)