From: Alexander Clouter <alex@digriz•org.uk>
To: netdev@vger•kernel.org
Subject: Re: setsockopt(IP_TOS) being privileged or distinct capability?
Date: Sat, 3 Jul 2010 19:55:30 +0100 [thread overview]
Message-ID: <2md4g7-3s3.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: 4C2F7A55.5090700@redfish-solutions.com
Philip Prindeville <philipp_subx@redfish-solutions•com> wrote:
>
> Does anyone else think that setsockopt(IP_TOS) should be a privileged
> operation, perhaps using CAP_NET_ADMIN, or maybe even adding separate
> granularity as CAP_NET_TOS?
>
I really would prefer not having to run telnet and ssh *clients* as
root. :)
Cheers
--
Alexander Clouter
.sigmonster says: Someday your prints will come.
-- Kodak
next prev parent reply other threads:[~2010-07-03 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-03 17:58 setsockopt(IP_TOS) being privileged or distinct capability? Philip Prindeville
2010-07-03 18:55 ` Alexander Clouter [this message]
2010-07-03 23:07 ` Philip Prindeville
2010-07-03 23:48 ` Alexander Clouter
2010-07-05 18:04 ` Philip Prindeville
2010-07-06 2:07 ` Hagen Paul Pfeifer
2010-07-06 3:08 ` Philip Prindeville
2010-07-06 3:13 ` David Miller
2010-07-06 10:56 ` Benny Amorsen
2010-07-05 18:08 ` Philip Prindeville
2010-07-06 8:17 ` Rémi Denis-Courmont
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=2md4g7-3s3.ln1@chipmunk.wormnet.eu \
--to=alex@digriz$(echo .)org.uk \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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