From: Arjan van de Ven <arjan@infradead.org>
To: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/1] /proc/$$/ipaddr and per-task networking bits
Date: Thu, 10 Mar 2005 15:26:21 +0100 [thread overview]
Message-ID: <1110464782.6291.95.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <1110464202.9190.7.camel@localhost.localdomain>
On Thu, 2005-03-10 at 15:16 +0100, Lorenzo Hernández García-Hierro
wrote:
> Ported feature from grSecurity that makes possible to add an ipaddr
> entry in each /proc/<pid> (/proc/<pid>/ipaddr), where the task originating
> IP address is stored, and subsequently made available (readable) by the process
> itself and also the root user with CAP_DAC_OVERRIDE capability (that can be managed
> by specific security models implementations like SELinux).
> Available also at http://pearls.tuxedo-es.org/patches/task-curr_ip.patch
a few questions
1) Why is this a config option; if it's useful it should just be always
on really
2) Can you explain briefly what this is useful for?
3) How does this work for existing stuff if, say, your dhcp lease
changes and your machine no longer owns a certain IP, what will happen
to the tasks?
4) if a machine has multiple IPs.. which one is chosen ?
next prev parent reply other threads:[~2005-03-10 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 14:16 Lorenzo Hernández García-Hierro
2005-03-10 14:26 ` Arjan van de Ven [this message]
2005-03-10 15:28 ` Lorenzo Hernández García-Hierro
2005-03-10 15:38 ` Arjan van de Ven
2005-03-10 16:00 ` Lorenzo Hernández García-Hierro
2005-03-10 16:08 ` Arjan van de Ven
2005-03-10 16:19 ` Paul P Komkoff Jr
2005-03-10 16:36 ` Joost Remijn
2005-03-11 12:35 ` Coywolf Qi Hunt
2005-03-10 15:22 ` YOSHIFUJI Hideaki / 吉藤英明
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=1110464782.6291.95.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@gnu.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
all inboxes | Powered by JetHome®