From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Andi Kleen <ak@suse.de>
Cc: kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org
Subject: Re: Multicast netlink for non-root process
Date: Tue, 11 Jun 2002 14:13:30 -0700 [thread overview]
Message-ID: <20020611141330.A22927@bougret.hpl.hp.com> (raw)
In-Reply-To: <20020611134418.A22893@bougret.hpl.hp.com.suse.lists.linux.kernel> <p737kl5cyw1.fsf@oldwotan.suse.de>
On Tue, Jun 11, 2002 at 11:02:22PM +0200, Andi Kleen wrote:
>
> There used to be a reason for it (ask Alexey for details), but it has gone.
> It should be safe now to remove it I think.
>
> -Andi
Ok, so let's ask Alexey ;-)
One potential reason is that some of the message may contain
data that is root only. But this should be handled with a finer
granularity.
One example : in the Wireless Extensions, when the user set
the WEP key, a RTNetlink message is generated indicating a change of
stateon the interface. This netlink message doesn't contain the WEP
key itself, the app has to request the key explicitely (and at that
point we catch the fact that the app is root or not).
If you really want to be clever, you could add a bit to the
netlink message to specify root only delivery (by the way of
netlink_broadcast()). In all cases, the data producer is the one that
knows what data is sensitive or not.
But, as currently it doesn't seem that any netlink message
that contain sensitive data (my WEP stuff beeing the exception and
taken care of), we could just lift this restriction.
Regards,
Jean
next prev parent reply other threads:[~2002-06-11 21:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020611134418.A22893@bougret.hpl.hp.com.suse.lists.linux.kernel>
2002-06-11 21:02 ` Andi Kleen
2002-06-11 21:13 ` Jean Tourrilhes [this message]
2002-06-11 21:23 ` Andi Kleen
2002-06-11 21:40 ` kuznet
2002-06-11 23:31 ` Andi Kleen
2002-06-11 23:55 ` Jean Tourrilhes
2002-06-12 4:25 ` James Morris
2002-06-12 17:25 ` kuznet
2002-06-12 17:45 ` James Morris
2002-06-12 17:54 ` kuznet
2002-06-12 22:53 ` David S. Miller
2002-06-11 20:44 Jean Tourrilhes
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=20020611141330.A22927@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=ak@suse.de \
--cc=jt@hpl.hp.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®