| Nuc1eoN | Hello guys, I am on eudev 3.2.10 and I am desperately trying to get my fido2 device (SoloKey) to work. I have tried everything according to the official docs: https://docs.solokeys.io/udev/ | 20:13 |
|---|---|---|
| Nuc1eoN | But the udev rules just do not make it work. | 20:13 |
| Nuc1eoN | E.g. this is my eudev rule: https://bpa.st/Z6VA | 20:13 |
| Nuc1eoN | I have even tested it with the command `udevadm test $(udevadm info --query=path --name=hidraw6)` and it appears to correctly fire the eudev rule: https://bpa.st/2NTQ | 20:13 |
| Nuc1eoN | But still, I can only access my fido2 device when I am root. My user is also in the plugdev group. But nothing makes it work. | 20:13 |
| Nuc1eoN | Do you guys have any suggestions? I am trying to get this to work for months... | 20:14 |
| rkta | I can't really help, but is this message about not being able to create the temporary db file expected? | 20:17 |
| rworkman | I'm about to have to run, but it's possible that you'll need the rule that sets GROUP of the device node; see the text "Older versions of udev use rules such as" on the solokeys.io page | 20:20 |
| rworkman | In essence, if the device node doesn't allow your user access, then you have to modify it to give that access. Making that device node be mode g+w and owned by group plugdev is one way to do that | 20:21 |
| rworkman | Maybe see "Which rule should I use, and how do I do it?" and (mostly) follow the advice in the first line below (Yubico's rule file) | 20:24 |
| rworkman | It looks like it will "just work" after that, based on a casual glance at the rules in that file (disclaimer: I do not have a solokey, so I can't say for sure) | 20:24 |
| rworkman | afk now | 20:24 |
| bb|hcb | Nuc1eoN: You say that the device works as root? So it seems that is a permission problem, and in your udev rules I do not see permissions specified; can you also share how the /dev entry looks like? | 20:28 |
| Arsen | show the rules you added | 20:31 |
| Nuc1eoN | With rworkman's advice I got it to work, I have copied the legacy rules file https://github.com/solokeys/solo/blob/master/udev/70-solokeys-legacy-access.rules to /lib/udev/rules.d. Thank you rworkman | 20:36 |
| Nuc1eoN | One issue is still left though. The rule did not work when I put it into /etc/udev/rules.d, and I found out using `udevatm test` that it did not process that directory at all. Is my eudev maybe set up incorrectly? Why wouldnt it look through /etc/udev/rules.d? | 20:36 |
| Arsen | hm, it certainly does for me | 20:37 |
| Arsen | I'm not sure that path is adjustable | 20:38 |
| Nuc1eoN | Maybe dudring compile time? | 20:38 |
| Arsen | it is adjustable at compile time, defaults to /etc/udev: https://github.com/eudev-project/eudev/blob/master/configure.ac#L174 | 20:39 |
| Nuc1eoN | Arsen, would it use the subfolder /etc/udev/rules.d ? | 20:40 |
| Nuc1eoN | Eudev definitely uses /etc/udev for me (there are some files belonging to eudev), but it does not seem to use the subfolder rules.d under that directory | 20:44 |
| Arsen | https://github.com/eudev-project/eudev/blob/226a9f4dedae29d22e333c215d32d25292da0a78/src/udev/udevd.c#L1308 definitely should be on | 20:46 |
| bb|hcb | ${prefix}/etc/udev/rules.d is processed by default; the rest depends on how eudev is compiled and also what is in its config file | 20:46 |
| bb|hcb | Nuc1eoN: what is your OS? | 20:46 |
| bb|hcb | I am guessing here: in case --prefix=/usr and there is no --sysconfdir=/etc, then it will look in /usr/etc/udev/rules.d/ | 20:52 |
| Arsen | oh, huh, that sounds a bit insane | 20:54 |
| bb|hcb | I have also verified that my eudev is processing /etc/udev/rules.d | 20:57 |
| Nuc1eoN | bb|hcb, thanks for the help. Frankly it is a bit esoteric, Im on GoboLinux, and here is the recipe I have used to build eudev https://github.com/gobolinux/Recipes/blob/master/Eudev/3.2.10/Recipe | 20:57 |
| bb|hcb | How does $settings_target resove there? | 20:58 |
| Nuc1eoN | Thats the funny part on gobo, here as an example you see how it works: | 21:00 |
| Nuc1eoN | https://bpa.st/X2GA | 21:00 |
| Nuc1eoN | /etc/udev is symlinked to /Programs/Eudev/Settings/udev | 21:00 |
| Nuc1eoN | However it does not seem to include rules.d for whatever reason | 21:01 |
| Nuc1eoN | Which is what I just noticed | 21:01 |
| bb|hcb | Maybe it looks in /Programs/Eudev/Settings/udev/rules.d instead? (I am guessing again, this is the first time I heard about GoboLinux) | 21:03 |
| Nuc1eoN | If I fiddle around enough maybe I manage to fix it, or I am gonna write to the gobolinux forums to get it fixed. I guess this topic is a bit outside of this irc channel. But it is awesome that we could debug the issue and actually get my solokey working, that is worth a lot to me already :) | 21:04 |
| Nuc1eoN | Before, I hadnt really a place to ask becasue eudev was abandoned | 21:05 |
| bb|hcb | yw (and I learned something new) :) | 21:06 |
| Nuc1eoN | bb|hcb, maybe if I figure it out I'll let you know what the issue was^^ | 21:07 |
| Nuc1eoN | but I guess it is something gobo specific | 21:07 |
| Nuc1eoN | if not, I am gonna come back anyways^^ | 21:08 |
| Nuc1eoN | Also if you ever feel like trying out something new I can recommend GoboLinux. It is actually a very well thought out distro. Only thing is you are more or less on your own :P | 21:10 |
| Nuc1eoN | But you learn a whole lot about linux | 21:10 |
| bb|hcb | It is, my advice is to mkdir /Programs/Eudev/Settings/udev/rules.d and symlink it to /etc/udev | 21:10 |
| Nuc1eoN | yes maybe that should have been symlinked, now I need to be careful though since /etc/udev/rules already contains rules by other programs. I guess I will move them to /Programs/Eudev/Settings/udev/rules.d first and then symlink (so that they dont disappear) | 21:21 |
| Nuc1eoN | for reference https://bpa.st/GJAA | 21:21 |
| Nuc1eoN | But those rules probably then never worked either^^ | 21:22 |
| rworkman | Nuc1eoN: glad you got it figured out. This is definitely something to discuss with GoboLinux maintainers - the rulesdir in /etc should absolutely be fixed. For information's sake, there's a (typically) /lib/udev/rules.d/ for rules that are installed with packages, and /etc/udev/rules.d/ for rules provided by sysadmins | 21:29 |
| bb|hcb | rworkman: it will take some time before all packages do follow the above rule ;) | 21:33 |
| Nuc1eoN | rworkman, yes I will speak with the other gobo maintainers about it:) | 21:38 |
| Nuc1eoN | And yeah, Fuse and Hplip seem not to follow the above rule^^ | 21:38 |
| rworkman | bb|hcb: indeed. I generally do patches and an MR/PR for projects when I come across them, but that's only if they have a contribution process that's easy to discover. If I have to spend more than a minute or so figuring how where to get source, where to send patches, etcetera, then oh well. I just fix it in our distro package and move on. | 21:40 |
| rworkman | Nuc1eoN: for hplip, something like this in installation process fixes it: make install DESTDIR=$PKG rulesdir=/lib/udev/rules.d | 21:42 |
| rworkman | For fuse, we move them manually in our packaging process. | 21:43 |
| rworkman | I wonder why I didn't push a patch to either of those :/ | 21:43 |
| bb|hcb | From what i have seen, the paths are fixed in distro packaging, while upstream packages install the rules in /etc/... | 21:49 |
| Nuc1eoN | This has been fixed in Fuse3 it seems. Some other packages also do it correctly -> https://bpa.st/7J6Q | 21:55 |
| Nuc1eoN | But still Fuse2 is required by a lot of programs. AppImage for instance. | 21:55 |
| Nuc1eoN | should probably be backported | 21:56 |
| Nuc1eoN | (At least I see 99-fuse3.rules is in the correct dir, while 99-fuse.rules isnt) | 21:57 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!