I finally took the time to make a pre-built .deb package for SiRFIDaL. I rewrote a few things so that it works (almost) right out of the box on Ubuntu and Debian as well as Linux Mint.
I went ahead and wrote a PKGBUILD for the Arch AUR for both SiRFIDaL and pyufr (Arch requires that all dependencies are installed, even for optional features, so I had to make a separate pyufr AUR package to fulfill that requirement).
Using any AUR helper, it should automatically pull and install the second AUR package, python-pyufr-git.
Itāll automatically install all files to their correct places, with the locations tweaked properly for Arch-based distros. Configuration must still be done as mentioned in the git repo, and the systemd services are disabled by default to ensure that proper configuration is done first.
Hopefully this helps Arch users get a quick start.
Iāve used a lot of Linux distros in the past 8 years, but I always find myself coming back to Arch. The lack of bloat, combined with setting up things the way I want, makes it a joy to come back to. The install process complexity is a bit overblown online, itās just reading the Installation Guide on the wiki. Takes me about 10 minutes to do an install, and it has all of the software I use ready for when I do my first boot. The AUR alone is a massive draw for me, I can always install the software I need (even if the software license doesnāt match the ethics of the distro maintainersā¦)
Itās also nice to always have up-to-date packages. When I ran Debian, even on testing, Iād run into bugs constantly that had already been fixed weeks prior.
If you try Arch at some point and find any packaging issues, feel free to let me know. Itās super easy for me to push changes to the PKGBUILD. I donāt have a lot of the reader hardware (serial readers for instance), so itās hard for me to 100% confirm that everything works.
If you make any changes to directory structure, try and make a post in this thread (or a README change), so I can make the necessary changes. The package is set up to pull the latest version of the git repo, so any changes in the files themselves will update in the AUR PKGBUILD automatically.
I started out with Slackware back in 1996 or something (so the complexity doesnāt bother me ), then worked professionally with Caldera OpenLinux (which was RPM-based) and finally settled on .deb-based distros because Iāve grown too lazy to fudge around with source packages and such anymore, and pre-chewed Linux distros pretty much Just Workā¢ nowadays. At least they work plenty well enough for what I want to do.
As for releasing stuff, I donāt want to touch RPM anymore (see above) but I do release .debs because they also Just Workā¢ for everybody else. Most people donāt like complexity.
I probably wonāt. You might have noticed that I keep everything in a flat directory, most of the Python code is self-contained (apart from the clients which use that one single class file) despite making the code really heavy, and everything is kept as āsmallest common denominatorā as possible - Including the full-ASCII README I do that on purpose to keep installation complexity and potential runtime problems to a minimum,
Sorry to change everything so soon since you made the Arch PKGBUILD: I was planning on switching the PAM module to pam_python eventually, but decided to do it after Mekhos mentioned he was unlocking his password manager using the autotyper. pam_python lets the SiRFIDaL PAM module bubble up the authentication token to Gnome Keyring Pam, so that itāll automatically unlock the keyring from the login credentials, which is a lot cleaner than the autotyper kludge. But of course it means rewriting the PAM module and changing the dependency, which is why I hadnāt done it. But I thought, what the hellā¦ So I did it. Sorry
This one adds the ability to copy UIDs into the system clipboard from the autotyper - something thatās rather needed if the user is to set their implant UID to unlock their password manager.
Sorry againā¦ Itās the weekend and Iām going back to the hospital tomorrow. So Iām cramming in as many new improvements as I can before Iām too out of commission.
Donāt worry, I should be done for some time now. Itās stuff I wanted to push in and it so happens that I had some quality time at home this weekend to do stuff I like.
Anyway, mekhos, if you want, you can install the latest version, then do this as root to reconfigure everything proper-like:
log out, log back in, then hold left-CTRL and left-ALT (or whatever you defined as hotkeys for the autotyper), scan your implant, copy the UID into the clipboard, then use the content of the clipboard as the new password for your keyring in KeePass.
That way, each time you log back in, the new SiRFIDaL PAM module will transfer your implantās UID to KeePass and that should unlock your keyring automatically upon login. It works fine with Gnome Keyring, and the KeePass literature claims itās compatible with Secret Service, so it should work the same way. That should take care of your issue by eliminating the need to autotype anything into KeePass altogether.
I modified a few things to make SiRFIDaL (mostly) compatible with RPM-based distributions out of the box - Fedora and such - and I created a RPM package for it.
Itās the Tasker script, but precompiled as a standalone app, so you donāt actually need Tasker or import the script into it manually. Just upload the APK file onto the cellphone somewhere, install it locally and run it (or, if youāre a geek, do adb install -r SiRFIDaL_NFC_reader.apk from your Linux box and run the app on the cellphone), and it should work the same way.
I tried it on the few test cellphones I have lying around and it seems to work okay, but it doesnāt behave quite the same way from one to the other. I you have a use for it, Iād be curious to know if it works correctly for you.
Tested on a phone running AOSP (no GSF), Android 11.
Developer mode and USB debugging enabled. A notification with āno active profilesā is displayed. When I scan, the SiRFIDaL app is an option for āchoose an actionā but selecting it does nothing.
It sounds like it works like itās supposed to. The only thing it does when it runs is expose card UIDs into the logfile for SiRFIDaL to read if itās connected.
If you enable the ADB listener in sirfidal_server_parameters.py, restart the server and connect your cellphone through USB, it should be visible in sirfidal_getuid.py when you scan your implant.
Nothing (Proxmark 3 working fine) I have enabled Android reader in sirfdal_server_parameters.py
Do I need latest version? Iām still on the one where the parameters files were simplifiedā¦~25th November
Maybe stop the server and type adb shell on the console. Iāve seen cases where the cellphone wonāt ask permission for debugging if adb isnāt run manually at least once.
The old version should work also. Functionally nothing has changed in the Android listener.
If it doesnāt work, donāt worry about it. I donāt want to waste your time.
