Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 1 Feb 2001 17:11:45 -0800
From:      Kris Kennaway <kris@obsecurity.org>
To:        Thomas Moestl <tmoestl@gmx.net>
Cc:        freebsd-audit@FreeBSD.ORG
Subject:   Re: patch to remove setgid kmem from top
Message-ID:  <20010201171145.A75869@xor.obsecurity.org>
In-Reply-To: <20010202015844.A1246@crow.dom2ip.de>; from tmoestl@gmx.net on Fri, Feb 02, 2001 at 01:58:44AM %2B0100
References:  <20010202015844.A1246@crow.dom2ip.de>

next in thread | previous in thread | raw e-mail | index | archive | help

--mP3DRpeJDSE+ciuQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Feb 02, 2001 at 01:58:44AM +0100, Thomas Moestl wrote:

> I have prepared a set of patches that allow running top as an ordinary
> user without setgid kmem.=20

Excellent!

> One sysctl, kern.lastpid, had to be added for this. It exports the=20
> nextpid variable, which reflects the highest PID used up to now.

Just to be clear, this isn't "the next PID which will be used by a
forked process", but "the PID of the last created process"? I'm pretty
sure the counter is incremented at fork-time (the issue is if we're
doing random PID increments to defeat prediction, we obviously don't
want to tip our hand). The latter is publically available information
and I don't see an issue with this.

Kris
--mP3DRpeJDSE+ciuQ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (FreeBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE6eglRWry0BWjoQKURAjfmAJ4uuQpWCjhfDLhLFZXlVy/ZGTvgNwCghmow
0+gxmf1hHHhh6dHNdYiKyM0=
=dwqm
-----END PGP SIGNATURE-----

--mP3DRpeJDSE+ciuQ--


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-audit" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010201171145.A75869>