lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 11 May 2017 23:07:55 +0200
From:   Pavel Machek <pavel@....cz>
To:     Michal Hocko <mhocko@...nel.org>
Cc:     Jingoo Han <jingoohan1@...il.com>,
        Lee Jones <lee.jones@...aro.org>, linux-fbdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: setting brightness as privileged operation?

On Thu 2017-01-05 10:23:07, Michal Hocko wrote:
> Hi,
> I have just learned that my Xfce Power Manager cannot manipulate
> brightness because I do not have policykit installed on my computer.
> There is a reason for that (yeah it depends on systemd which I prefer
> not have).
> 
> While this is clearly a problem of the Xfce applet I am wondering why
> setting the brightness has to be a privileged operation at all. Is there
> any strong reason for it or just a general policy that we do not give
> world writable files into sysfs?

Well, if you have another user logged in using ssh, and changing _your_
brightness, that will be somehow annoying, right?

That's the reason why global settings should be root-only...

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ