netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "arun" <akumar@omnesysindia.com>
To: <netdev@oss.sgi.com>
Subject: SIOCETHTOOL history ?
Date: Tue, 6 May 2003 18:07:48 +0530	[thread overview]
Message-ID: <01f301c313cc$4e6cb8b0$243205c0@otp.com> (raw)

 Hi,
 
 Can anyone of the veterans please help me out with a 
small code curiosity

Why does the SIOCETHTOOL ioctl need 
CAP_NET_ADMIN even for harmless commands  like 
GSET ?

Some sample drivers that I managed to download over the net
that supports SIOCETHTOOL  has comments like 

"no need to check for CAP_NET_ADMIN since that is already
present in net/core/dev.c".  (And sure enough it was there)

Why would such a blanket checking be present when this ioctl
is only an entry point for many sub commands ? 

I have used SIOCGMIIPHY before and it seemed not to require 
any su rights or capabilities. What's then the difference between these
2 ioctls that require more capabilities for SIOCETHTOOL ?

arun

             reply	other threads:[~2003-05-06 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 12:37 arun [this message]
2003-05-06 11:49 ` SIOCETHTOOL history ? David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2003-05-06 13:24 arun

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='01f301c313cc$4e6cb8b0$243205c0@otp.com' \
    --to=akumar@omnesysindia.com \
    --cc=netdev@oss.sgi.com \
    /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).