On Wed, Mar 13, 2024 at 7:05 PM Ron Flory via users
<users@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
>
> does not happen on FC38, or any prior RedHat/Fedora version since forever.
>
> dmesg
> dmesg: read kernel buffer failed: Operation not permitted
>
> Userspace scripts (such as used to read pics from cameras & sdcards) and many progs often use dmesg to detect or identify things like startup probe info, USB devs, partition numbers etc.
>
> I worked around this by setting the suid bit of `which dmesg`, but it would be rude to force everybody to manually do this as part of post-install cleanup.
>
> Hopefully an unintended side-effect and not a new "feature" that wasn't thought through completely. A web-search suggests debian/ubuntu may have been doing this for awhile- but we really don't need to be just like them... ;)
You can restore old behavior with the following.
# sysctl kernel.dmesg_restrict=0
Put in /etc/sysctl.d/10-dmesg.conf to make it permanent.
Jeff
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
