Happy to help! For me, python was the way to get everything I wanted, instead of almost what I needed. In my opinion, the python-evdev documentation is really helpful, and should be able to get you most of the way to what you need. For what it's worth, based on my experience with AutoHotKey on Windows, you should be able to recreate anything you had before and more with python.
Overdraft
joined 1 year ago
How do I emulate mouse clicks via keyboard shortcuts while gaming on Linux? (aka AutoHotkey on Linux)
How do I emulate mouse clicks via keyboard shortcuts while gaming on Linux? (aka AutoHotkey on Linux)
How do I emulate mouse clicks via keyboard shortcuts while gaming on Linux? (aka AutoHotkey on Linux)
I went on a journey to do something very similar, I remap keypad buttons to various other inputs using a python script running as a service. My original post is here, and my eventual solution is in the comments. My post has some links to other solutions that I tried, but ultimately I'm happy using a custom python script. That may not fit your need, but maybe it will help a little!
The Guardian references an NPR article where they discuss the vulnerability as a phishing attack, so it doesn't seem to be anything interesting after all.
https://www.npr.org/2025/03/25/nx-s1-5339801/pentagon-email-signal-vulnerability
Edit: Once you "grab" your input device with python-evdev (
dev.grab()
), the input will be absorbed until it is un-grabed (dev.ungrab()
). If you grab your only keyboard input, you'll be stuck and will need a secondary keyboard to get unstuck.I have a bad habit of speculating too much, I'm gonna try to stick to just what I did in case I'm remembering some of the why details incorrectly. I'll use the details from my device, anywhere you see "Azeron LTD Azeron Keypad", "16d0", or "1103", you need to replace the values with your device-
Start by finding the info for the input device you want to monitor:
This should result in a list of input devices with various details, I used the 'Name' to identify mine:
When you have found the device, save the vendor ID and product ID for the next step:
Add a udev rule so that you can read the input from the device, and another for python-evdev to create a virtual device. I use link_priority 71 (as seen in the file name). The rule I'm using to let the virtual device be created could be better - this is something you might want to research more for a permanent solution, but this rule can be removed later if you just wanted to test with it:
Write the file contents:
Restart udev:
At this point, you should have access to the device from python-evdev and also be able to create a virtual device with python-evdev. I don't know if it will help, but I figured I can add a bit of my code here:
The code above I run as a service, but my explanation is getting a bit long-winded already, so if any of this ends up being helpful, and you actually do want to run it as a background service, if you need help doing that let me know!