Upcoming lirc package for openSUSE:Factory

Edit Package lirc

This package will be submitted to openSUSE:Factory soon. All changes for the Factory package should get tested here first.

Refresh
Refresh
Source Files
Filename Size Changed
baselibs.conf 0000000081 81 Bytes
harden_irexec.service.patch 0000000683 683 Bytes
harden_lircd-uinput.service.patch 0000000727 727 Bytes
harden_lircd.service.patch 0000000764 764 Bytes
harden_lircmd.service.patch 0000000734 734 Bytes
lirc-0.10.1.tar.bz2 0002523226 2.41 MB
lirc-autoconf-py310.patch 0000516112 504 KB
lirc.changes 0000048859 47.7 KB
lirc.spec 0000012441 12.1 KB
pyyaml-60-compatibility.patch 0000002147 2.1 KB
reproducible.patch 0000002509 2.45 KB
Revision 110 (latest revision is 119)
Stefan Seyfried's avatar Stefan Seyfried (seife) accepted request 931284 from Ludger Dreier's avatar Ludger Dreier (ldreier) (revision 110)
lircd: allow input device access in lircd.service again
Comments 3

Ludger Dreier's avatar

Additions from harden_lircd.service.patch broke lircd for me. Now error "lircd-0.10.1[19958]: Error: unable to open '/dev/input/event8'" (example) is written periodically to journal logs. Proposed fix (that worked for me): add "DeviceAllow=char-input" to the lircd.service file

Background: Seems to be related to ProtectClock=true https://en.opensuse.org/openSUSE:Security_Features#Systemd_hardening_effort states: ProtectClock: 'true' (implies DeviceAllow=char-rtc r, which implies a restriction on all other devices, so breaks e.g. everything trying to access a disk device without further DeviceAllow= lines) So "/dev/input/eventX" is "other devices"...


Stefan Seyfried's avatar

The package's maintainer seems to be no longer active, so either file a bug for the security team, or, as you seem to have found the cause already, just submit a fix for the package ;-)


Ludger Dreier's avatar

Submitted a fix for that in https://build.opensuse.org/request/show/931284 some days ago, currently still pending.

openSUSE Build Service is sponsored by