From: David Martin <tasio@tasio.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] pid randomness
Date: Mon, 27 Dec 2004 21:01:54 +0100 [thread overview]
Message-ID: <200412272101.54370.tasio@tasio.net> (raw)
In-Reply-To: <41D064D5.1030900@rnl.ist.utl.pt>
Hi,
You have an implementation of this and other stuff on grsecurity
(www.grsecurity.net) patch for both 2.4 and 2.6 kernel. It is intented for
servers, critical machines, or just paranoic users :)
cheers,
david.
On Monday 27 December 2004 20:39, you wrote:
> hi everyone,
>
> I don't know if this has been discussed before... but I'd like to ask
> why isn't the pids randomized by default?
>
> I mean, of course it's not required for normal functioning but it'd be
> nice to have a Kconfig option to make it happen.
>
> The (newbie) way I see it, it'd not be hard to do... generate pid, check
> if it's unique, give pid to process. It could bring some minor security
> enhancements while taking a slight performance hit (seek & compare
> algorithm for used pids).
>
> What are the pros and cons of this? What are your oppinions on this subjet?
>
> regards,
> pedro venda.
--
This device complies with part 15 of the FCC rules. Operation is
subject to the following two conditions:
(1) This device may not cause harmful interference,
(2) This device must accept any interference received, including
interference that may cause undesired operation.
next prev parent reply other threads:[~2004-12-27 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 19:39 Pedro Venda (SYSADM)
2004-12-27 19:47 ` Jan Engelhardt
2004-12-27 20:04 ` Pedro Venda (SYSADM)
2004-12-27 20:01 ` David Martin [this message]
2004-12-27 20:45 ` Valdis.Kletnieks
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=200412272101.54370.tasio@tasio.net \
--to=tasio@tasio.net \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®