From: Stephen Hemminger <shemminger@vyatta.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: David Miller <davem@davemloft.net>,
Jeff Garzik <jgarzik@pobox.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH] ethtool: allow non-netadmin to query settings
Date: Mon, 23 Aug 2010 14:40:41 -0700 [thread overview]
Message-ID: <20100823144041.6a88c0ed@nehalam> (raw)
In-Reply-To: <1282598678.2267.85.camel@achroite.uk.solarflarecom.com>
On Mon, 23 Aug 2010 22:24:38 +0100
Ben Hutchings <bhutchings@solarflare.com> wrote:
> On Mon, 2010-08-23 at 13:24 -0700, Stephen Hemminger wrote:
> > The SNMP daemon uses ethtool to determine the speed of
> > network interfaces. This fails on Debian (and probably elsewhere)
> > because for security SNMP daemon runs as non-root user (snmp).
> >
> > Note: A similar patch was rejected previously because of a concern about
> > the possibility that on some hardware querying the ethtool settings
> > requires access to the PHY and could slow the machine down. But the
> > security risk of requiring SNMP daemon (and related services)
> > to run as root far out weighs the risk of denial-of-service.
> [...]
>
> Speed and duplex are now exposed through world-readable attributes in
> sysfs. Currently this is implemented by calling the ethtool
> get_settings() operations but that could be improved on by adding speed
> and duplex fields to struct net_device or by allowing drivers to
> implement a cheaper operation that provides just this information.
>
Changing daemon is possible, but changing every driver to do this
is not a practical option.
next prev parent reply other threads:[~2010-08-23 21:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 20:24 [PATCH] ethtool: allow non-netadmin to query settings Stephen Hemminger
2010-08-23 21:24 ` Ben Hutchings
2010-08-23 21:40 ` Stephen Hemminger [this message]
2010-08-24 3:44 ` David Miller
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=20100823144041.6a88c0ed@nehalam \
--to=shemminger@vyatta.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=jgarzik@pobox.com \
--cc=netdev@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).