From: David Miller <davem@davemloft.net>
To: nenolod@atheme.org
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2.6.18 try 2] net/ipv4: sysctl to allow non-superuser to bypass CAP_NET_BIND_SERVICE requirement
Date: Fri, 22 Sep 2006 11:04:36 -0700 (PDT) [thread overview]
Message-ID: <20060922.110436.34753480.davem@davemloft.net> (raw)
In-Reply-To: <AD838733-3A8F-4B3E-B620-9B2284B8B2BF@atheme.org>
From: William Pitcock <nenolod@atheme.org>
Date: Fri, 22 Sep 2006 03:27:22 -0500
> * The software is untrusted by the end user, in the event that the
> software is not trustworthy, the amount of damage it can do running
> as a normal user is less than as a superuser. As it is, the bind()
> may have failed before the CAP_NET_BIND_SERVICE capability was
> granted to the process.
You have the power to exec() the daemon in question with
CAP_NET_BIND_SERVICE capability inherited from the parent,
and that will be the only "extra" capability the process will
have.
So there is in fact an existing mechanism for doing this.
If you have the power to set the sysctl, you have the power
to give the capability to an arbitrary process which you
want to get lower ports but do not trust to run completely
as root.
prev parent reply other threads:[~2006-09-22 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E1176C1-8F18-4790-9BCB-95306ACED48A@atheme.org>
[not found] ` <736CE60D-FB88-4246-8728-B7AC7880B28E@atheme.org>
2006-09-22 7:41 ` [PATCH 2.6.18 try 2] net/ipv4: sysctl to allow non-superuser to bypass CAP_NET_BIND_SERVICE requirement YOSHIFUJI Hideaki / 吉藤英明
2006-09-22 8:22 ` William Pitcock
2006-09-22 8:27 ` William Pitcock
2006-09-22 18:04 ` David Miller [this message]
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=20060922.110436.34753480.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nenolod@atheme.org \
--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).