Upcoming lirc package for openSUSE:Factory
This package will be submitted to openSUSE:Factory soon. All changes for the Factory package should get tested here first.
- Devel package for openSUSE:Factory
-
6
derived packages
- Links to openSUSE:Factory / lirc
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout vdr/lirc && cd $_ - Create Badge
Refresh
Refresh
Source Files
| Filename | Size | Changed |
|---|---|---|
| baselibs.conf | 0000000081 81 Bytes | |
| harden_irexec.service.patch | 0000000664 664 Bytes | |
| harden_lircd-uinput.service.patch | 0000000708 708 Bytes | |
| harden_lircd.service.patch | 0000000663 663 Bytes | |
| harden_lircmd.service.patch | 0000000715 715 Bytes | |
| lirc-0.10.1.tar.bz2 | 0002523226 2.41 MB | |
| lirc-autoconf-py310.patch | 0000516112 504 KB | |
| lirc.changes | 0000048839 47.7 KB | |
| lirc.spec | 0000012556 12.3 KB | |
| pyyaml-60-compatibility.patch | 0000002147 2.1 KB | |
| reproducible.patch | 0000002509 2.45 KB |
Revision 103 (latest revision is 119)
Stefan Seyfried (seife)
accepted
request 910628
from
Stanislav Brabec (sbrabec)
(revision 103)
- Require typelib packages, otherwise lirc-setup fails to start.
Comments 3
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"...
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 ;-)
Submitted a fix for that in https://build.opensuse.org/request/show/931284 some days ago, currently still pending.