Replies: 2 comments 1 reply
-
Hi @m1st0, thank you for your request! It should be possible to remove the need for running as the I got it mostly working using a dedicated user and group ( # set up user
sudo useradd -r eruption -s /usr/sbin/nologin -d /
sudo usermod -a -G input eruption
# dirs and permissions
sudo mkdir /run/eruption
sudo chown eruption /run/eruption
sudo chown -R eruption:eruption /var/lib/eruption/
# permissions in /dev
sudo setfacl /dev/uinput -m u:eruption:rw
# run eruption as non-root
sudo -u eruption -g eruption RUST_LOG=debug RUST_BACKTRACE=full target/debug/eruption -c support/config/eruption-dev.conf
I will try to polish the changes somewhat and then merge them to the |
Beta Was this translation helpful? Give feedback.
0 replies
-
Made a branch to test this, but can't build at the moment:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I was trying to look into required permissions. With some other keyboard LED projects, I've been able to work with hardware using udev rules in Ubuntu at /etc/udev/rules.d/ 51-hv-kb395l-keyboard.rules such as the following for that keyboard
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="04d9", ATTRS{idProduct}=="a1dd", TAG+="uaccess"
or in the case of a Vulcan 121 AIMO I tried
ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="1e7d", ATTRS{idProduct}=="3098", TAG+="uaccess"
Of course this was just a test and there are other needs in the software for more access rights over just the hardware. I was just wondering if we can go this route and remove the need for root access?
Beta Was this translation helpful? Give feedback.
All reactions