From: Pavel Machek <pavel@ucw.cz>
To: Michal Hocko <mhocko@kernel.org>
Cc: Jingoo Han <jingoohan1@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: setting brightness as privileged operation?
Date: Fri, 12 May 2017 09:47:12 +0000 [thread overview]
Message-ID: <20170512094712.GA29780@amd> (raw)
In-Reply-To: <20170512062003.GB6803@dhcp22.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
On Fri 2017-05-12 08:20:04, Michal Hocko wrote:
> On Thu 11-05-17 23:07:55, Pavel Machek wrote:
> > 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?
>
> I am pretty sure that such a user can do much larger harm than playing
> with brigtness of my LCD. Anyway I went with my own rc.local hack.
Can he? Those are bugs to be fixed. We don't want them in kernel...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-05-12 9:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 9:23 setting brightness as privileged operation? Michal Hocko
2017-05-11 21:07 ` Pavel Machek
2017-05-12 6:20 ` Michal Hocko
2017-05-12 9:47 ` Pavel Machek [this message]
2017-05-17 11:02 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170512094712.GA29780@amd \
--to=pavel@ucw.cz \
--cc=jingoohan1@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).