Bug 631096

Summary:	app-crypt/libu2f-host - USE=systemd is not properly working
Product:	Gentoo Linux	Reporter:	Bertrand Jacquin <bertrand>
Component:	Current packages	Assignee:	Crypto team [DISABLED] <crypto+disabled>
Status:	RESOLVED INVALID
Severity:	normal	CC:	bertrand
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Bertrand Jacquin 2017-09-15 22:56:47 UTC

Hi,

I am currently using systemd and app-crypt/libu2f-host build with USE=systemd actually does not allow me to use at all my U2F token.

$ curl 'https://demo.yubico.com/wsapi/u2f/enroll?username=jas&password=foo' > foo
$ u2f-host --debug -aregister -o https://demo.yubico.com < foo > bar
error: u2fh_devs_discover (-5): cannot find U2F device

Building it with USE=-systemd allow me to perform authentication.

Reproducible: Always

Comment 1 Bertrand Jacquin 2017-09-18 23:17:46 UTC

Actually it works with USE=systemd, but default permission on /dev/hidraw* are not letting standard users to read the char device:

$ ls -l /dev/hidraw*
crw------- 1 root root 249, 0 Sep 19 00:04 /dev/hidraw0
crw------- 1 root root 249, 1 Sep 19 00:02 /dev/hidraw1

Comment 2 Bertrand Jacquin 2017-09-23 00:28:49 UTC

This bug is invalid, my X11 session was running outside of a systemd session, hence files created in /dev did not have the right ACL