From: Michael Buesch <mb@bu3sch.de>
To: Andy Green <andy@warmcat.com>
Cc: linux-wireless@vger.kernel.org,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Permissions down /sys
Date: Mon, 9 Jul 2007 22:57:25 +0200 [thread overview]
Message-ID: <200707092257.25909.mb@bu3sch.de> (raw)
In-Reply-To: <469297DF.4000806@warmcat.com>
On Monday 09 July 2007 22:17:35 Andy Green wrote:
> Hi folks -
>
> Is 222 permissions on /sys/class/ieee80211/phy*/add_iface and
> remove_iface really okay, or should it perhaps be 220?
>
> --w--w--w- 1 root root 0 2007-07-09 21:11 add_iface
> --w--w--w- 1 root root 4096 2007-07-09 21:12 remove_iface
IMO the file-permissions are correct, _but_ the following should
be added to _store_remove_iface() and _store_add_iface():
if (!capable(CAP_NET_ADMIN))
return -EPERM;
--
Greetings Michael.
next prev parent reply other threads:[~2007-07-09 20:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 20:17 Permissions down /sys Andy Green
2007-07-09 20:57 ` Michael Buesch [this message]
2007-07-09 21:03 ` Andy Green
2007-07-10 12:57 ` Johannes Berg
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=200707092257.25909.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=andy@warmcat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.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).