From: William Hubbs <w.d.hubbs@gmail.com>
To: Christopher Brannon <chris@the-brannons.com>
Cc: Greg KH <greg@kroah.com>, kirk@braille.uwo.ca, speakup@braille.uwo.ca
Subject: Re: World writable speakup files in Linux next
Date: Sat, 11 Dec 2010 16:28:34 -0600 [thread overview]
Message-ID: <20101211222834.GA27436@linux1> (raw)
In-Reply-To: <87lj3wufx7.fsf@the-brannons.com>
On Sat, Dec 11, 2010 at 10:02:12PM +0000, Christopher Brannon wrote:
> Greg KH <greg@kroah.com> writes:
>
> > As I don't want to just blindly remove the world writable permissions on
>
> Hah, hah! This is very punny, though I'm certain that you didn't intend
> to make a pun. (Highlighting *blindly*).
>
> > all of these files, could someone go through and verify which ones
> > should and should not be world writable?
>
> Personally, I'd say ditch the world-readable bit. We should deal with
> this in terms of groups. The only user who should really be able to
> write to these files is the one sitting at the console.
Do we know for sure that udev can manipulate the group ownership of
files in the /sys hierarchy? I'll be the first to admit that I have only
briefly looked at udev, but I don't think we should remove the world
writable bit until we know for sure whether udev can do anything with
the /sys hierarchy.
Thanks,
William
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101210190047.GA19219@kroah.com>
` William Hubbs
` Frost
` Christopher Brannon
` William Hubbs [this message]
` Samuel Thibault
[not found] ` <20101212182940.GB16883@kroah.com>
` Kirk Reiser
` Samuel Thibault
` Kirk Reiser
` Samuel Thibault
` acollins
` Samuel Thibault
` Frost
` Samuel Thibault
` Kitty Litter
` Samuel Thibault
` Frost
` bardiazakeri
` Frost
` bardiazakeri
` Littlefield, Tyler
` bardiazakeri
` Kerry Hoath
` Littlefield, Tyler
` Arch Linux was: " Øyvind Lode
` bardiazakeri
` speakup and ubuntu, was: " Gregory Nowak
` Littlefield, Tyler
` Samuel Thibault
` Michael Whapples
` Samuel Thibault
` Frost
` bardiazakeri
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=20101211222834.GA27436@linux1 \
--to=w.d.hubbs@gmail.com \
--cc=chris@the-brannons.com \
--cc=greg@kroah.com \
--cc=kirk@braille.uwo.ca \
--cc=speakup@braille.uwo.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).