On Tue, Mar 15, 2022 at 6:57 PM Julian Gilbey wrote: > euler:~ $ xscreensaver -no-splash > xscreensaver-auth: 17:48:30: OOM: /proc/7427/oom_score_adj: Permission denied > xscreensaver-auth: 17:48:30: To prevent the kernel from randomly unlocking > xscreensaver-auth: 17:48:30: your screen via the out-of-memory killer, > xscreensaver-auth: 17:48:30: "xscreensaver-auth" must be setuid root. > > And: > > euler:~ $ ls -l /usr/libexec/xscreensaver/xscreensaver-auth > -rwxr-xr-x 1 root root 308168 Jan 15 15:40 > /usr/libexec/xscreensaver/xscreensaver-auth > > So perhaps this should be setuid root?
Thanks for the report. I guess this is something we'll leave to the local administrator, to consider whether the risk of random unlocking is worse than another setuid executable. xscreensaver is quite safe with the recent split-out of xscreensaver-auth though. Best regards, Tormod
