From: Andrea Veri <andrea.veri89@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: rfkill read / write access needs to be enabled for normal users
Date: Sun, 25 Oct 2009 12:48:21 +0100 [thread overview]
Message-ID: <20091025124821.7236d733@bluepaper> (raw)
In-Reply-To: <1256401467.7812.7.camel@localhost.localdomain>
Il giorno Sun, 25 Oct 2009 01:24:27 +0900
Marcel Holtmann <marcel@holtmann.org> ha scritto:
> I have said this before and let me repeat it again, gnome-bluetooth
> should not mess directly with the RFKILL subsystem. It is the wrong
> approach and that is the reason why normal users don't have
> uncontrolled access to /dev/rfkill.
yeah, I know. That's why I didnt apply the patch yet, but indeed this
needs to be fixed ASAP, so my question is what can I do in the meantime
to have it fixed? (e.g while upstream implement it directly into bluez)
is the patch proposed by Bastien, the only one available for *now*?
Thanks for your work,
Andrea
prev parent reply other threads:[~2009-10-25 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 15:13 rfkill read / write access needs to be enabled for normal users Andrea Veri
2009-10-24 16:24 ` Marcel Holtmann
2009-10-24 17:28 ` Bastien Nocera
2009-10-25 11:48 ` Andrea Veri [this message]
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=20091025124821.7236d733@bluepaper \
--to=andrea.veri89@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.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