From: Radoslaw Szkodzinski (AstralStorm) <lkml@astralstorm.puszkin.org>
To: "Mikael Ståldal" <mikael.staldal@univits.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possibility to adjust the only-root-can-bind-to-port-under-1024 limit
Date: Tue, 20 Nov 2007 20:23:06 +0100 [thread overview]
Message-ID: <20071120202306.65e6036c@astralstorm.puszkin.org> (raw)
In-Reply-To: <474306BF.4010207@univits.com>
[-- Attachment #1: Type: text/plain, Size: 755 bytes --]
On Tue, 20 Nov 2007 17:09:35 +0100
Mikael Ståldal <mikael.staldal@univits.com> wrote:
> Hello.
>
> > The proper way to enable port <= 1024 binding support is adding CAP_NET_BIND_SERVICE
> > to the process capability set, e.g. by using file-system capabilities.
>
> Is file-system capabilites part of the stable official Linux kernel? From which version?
> How do I use it?
>
They were recently added in 2.6.24-rc1.
(mostly commit b53767719b6cd8789392ea3e7e2eb7b8906898f0)
The patch should be easy to backport, I've seen it in various
distro kernels.
According to the commit, documentation is at
http://www.friedhoff.org/fscaps.html
Some programs already have capability support - they
drop all permissions they don't need.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-11-20 19:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 10:14 Possibility to adjust the only-root-can-bind-to-port-under-1024 limit Mikael Ståldal
2007-11-20 14:53 ` Radoslaw Szkodzinski
[not found] ` <474306BF.4010207@univits.com>
2007-11-20 19:23 ` Radoslaw Szkodzinski [this message]
2007-11-26 9:52 ` Mikael Ståldal
2007-11-27 22:42 ` Phillip Susi
2007-11-30 9:15 ` Mikael Ståldal
[not found] <554627.38779.qm@web36601.mail.mud.yahoo.com>
2007-12-06 12:32 ` Mikael Ståldal
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=20071120202306.65e6036c@astralstorm.puszkin.org \
--to=lkml@astralstorm.puszkin.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikael.staldal@univits.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).