Your message dated Wed, 16 Sep 2020 18:48:24 +0000
with message-id <[email protected]>
and subject line Bug#970421: fixed in chrony 3.5.1-2
has caused the Debian Bug report #970421,
regarding apparmor limit blocks temperature reading
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
970421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970421
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chrony
Version: 3.4-4
Current apparmor profile for chrony lists
@{sys}/class/hwmon/hwmon[0-9]*/temp[0-9]*_input r,
which is great (and even how I have mine configured -
tempcomp /sys/class/hwmon/hwmon0/temp1_input 1 0 0 0 0) but it doesn't actually
work. It results in lots of log lines like
Sep 15 23:06:37 gw.as397444.net audit[24397]: AVC apparmor="DENIED" operation="open" profile="/usr/sbin/chronyd"
name="/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input" pid=24397 comm="chronyd" requested_mask="r"
denied_mask="r" fsuid=112 ouid=0
Sep 15 23:06:37 gw.as397444.net chronyd[24397]: Could not read temperature from
/sys/class/hwmon/hwmon0/temp1_input
Sep 15 23:06:37 gw.as397444.net kernel: audit: type=1400 audit(1600225597.313:127): apparmor="DENIED" operation="open"
profile="/usr/sbin/chronyd" name="/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input" pid=24397
comm="chronyd" requested_mask="r" denied_mask="r" fsuid=112 ouid=0
Looks like somehow apparmor is resolving the file to a different path,
checking, and then failing it.
An extra line like the following fixes it:
@{sys}/devices/virtual/thermal/thermal_zone[0-9]*/hwmon[0-9]*/temp[0-9]*_input
r,
Matt
--- End Message ---
--- Begin Message ---
Source: chrony
Source-Version: 3.5.1-2
Done: Vincent Blut <[email protected]>
We believe that the bug you reported is fixed in the latest version of
chrony, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Vincent Blut <[email protected]> (supplier of updated chrony package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Wed, 16 Sep 2020 12:32:23 +0200
Source: chrony
Architecture: source
Version: 3.5.1-2
Distribution: unstable
Urgency: medium
Maintainer: Vincent Blut <[email protected]>
Changed-By: Vincent Blut <[email protected]>
Closes: 970421
Changes:
chrony (3.5.1-2) unstable; urgency=medium
.
[ Matt Corallo ]
* debian/usr.sbin.chronyd:
- Fix temperature reading. (Closes: #970421)
Checksums-Sha1:
0c7d95f1f13f07cc2325aa94a758703b7d08693d 2119 chrony_3.5.1-2.dsc
83f82d1f4696113b819646d3c73166faab5c4479 37072 chrony_3.5.1-2.debian.tar.xz
Checksums-Sha256:
f73bc5c63ecca2fa9be2c87fedd51c5e26597f9a56a7167e2891fa77aa215ae3 2119
chrony_3.5.1-2.dsc
017e4f80a87ffd708a0c2d780428a8c4785b8035221420114516f48cd6f1a80b 37072
chrony_3.5.1-2.debian.tar.xz
Files:
9c2f473d2e4ca0cbf31f6458fcb06b79 2119 net optional chrony_3.5.1-2.dsc
d48509ddf5326588321e5c9e7651aa4e 37072 net optional
chrony_3.5.1-2.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAl9iWH4ACgkQnFyZ6wW9
dQotrQf+MbplW6bJ7RdVlkxZ3jwvjPydddmRycD8ckdqck9s7ph5iTsEpNUSM2Q8
5mo7VgkPR8RZG28o8g8qOmWsalrP9kvGWxTyoZgIgbAXeDdamM7UCmaL/WqMZDwQ
Hwadn2FJWgFyzo4QKfdCXpJhTPFTHHf3sUL3mwhp/8bW5LfGyViVEJ8sTkcFgoIC
ir5BsC2+uqDaw4xFDVanwfRgx1mpNldc6/s+HDXjBh9vU2Fvb65cJwghQQJboeTk
VkRQXohu4iqHhGYPO4C7do/hrQ//1/wRKnKt387ycZ7FodHconIRhvBwmXYvvpVt
Y2L5Q3SItmJ1mi3u2CXYZdQ/tsspNg==
=7xF/
-----END PGP SIGNATURE-----
--- End Message ---