Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#41895 - [hackrf] [PATCH] Unsufficient device permission in udev rule

Attached to Project: Community Packages
Opened by Dominik Heidler (asdil12) - Tuesday, 09 September 2014, 21:33 GMT
Last edited by Kyle Keen (keenerd) - Sunday, 27 December 2015, 19:54 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Kyle Keen (keenerd)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

The current device permissions in the udev rules file of hackrf are "660".
This way the hackrf device can only be operated as root.
As most software (eg. gqrx) is not meant to be run as root, the device should be accessable by the user as it is already the case eg. with rtl-sdr.
   hackrf_chmod.patch (0.4 KiB)
This task depends upon

Closed by  Kyle Keen (keenerd)
Sunday, 27 December 2015, 19:54 GMT
Reason for closing:  Fixed
Additional comments about closing:  hackrf-2015.07.2-2
Comment by Dave Reisner (falconindy) - Tuesday, 09 September 2014, 22:21 GMT
So we go from insufficient to insecure? Making the node world writeable is no "solution". I'd suggest bringing this up with upstream first, since your sed hack is patching one of their files, and not a file provided by Arch.
Comment by Dominik Heidler (asdil12) - Tuesday, 09 September 2014, 22:27 GMT
A clean solution would be IMHO to have a group that I could add a user to, in order to access the device.
But the package would need to create that group.
And we would still need a sed call as upstream specified *plugdev*, which exists on ubuntu but not on arch.

Maybe we could get a common *radio* group for that kind of devices.
Comment by Kyle Keen (keenerd) - Wednesday, 10 September 2014, 00:25 GMT
We'll just use plugdev. It is already the group for a couple of other (aur) packages. You'll have to manually create the group however, and the postinstall will provide instructions.
Comment by Damjan Georgievski (damjan) - Friday, 31 July 2015, 00:59 GMT
udev still complains about plugdev, and there doesn't seem to be post-install message about it.

ps.
the same is true for airspy 1.0.3-2 too
Comment by Allen Welkie (awelkie) - Saturday, 29 August 2015, 02:17 GMT
Instead of specifiying a group in the udev rules file, could you just add `TAG+="uaccess"`? See the following references:

https://wiki.archlinux.org/index.php/Talk:Udev#Use_of_.27uaccess.27_instead_of_GROUP_and_MODE.3F
http://cgit.freedesktop.org/systemd/systemd/tree/src/login/70-uaccess.rules
https://bugzilla.redhat.com/show_bug.cgi?id=1074122
https://github.com/pwr/Solaar/issues/66

This worked for me without having to add the plugdev group.

Loading...