From owner-freebsd-security Thu Jul 12 8:33:20 2001 Delivered-To: freebsd-security@freebsd.org Received: from ringworld.nanolink.com (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id EE91137B405 for ; Thu, 12 Jul 2001 08:33:11 -0700 (PDT) (envelope-from roam@orbitel.bg) Received: (qmail 1922 invoked by uid 1000); 12 Jul 2001 15:37:21 -0000 Date: Thu, 12 Jul 2001 18:37:21 +0300 From: Peter Pentchev To: rich@rdrose.org Cc: freebsd-security@freebsd.org Subject: Re: kern.randompid Message-ID: <20010712183721.B849@ringworld.oblivion.bg> Mail-Followup-To: rich@rdrose.org, freebsd-security@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from rich@rdrose.org on Thu, Jul 12, 2001 at 04:07:44PM +0100 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, Jul 12, 2001 at 04:07:44PM +0100, rich@rdrose.org wrote: > Hi, > > Any reason why this happens (consistently) on a 4.3-RELEASE machine? > > shrek# sysctl -w kern.randompid=1 > kern.randompid: 0 -> 0 > > Given that I also have kern.randompid=1 in my /etc/sysctl.con, it should > already be 1.. but it isn't... The kern.randompid sysctl is not a boolean flag, but an estimate of the random value that will be added to each newly created pid. For more information, read the comments in src/sys/kern/kern_fork.c before the sysctl_kern_randompid() function (around line 150). The function itself ignores sysctl settings of less than 2. G'luck, Peter -- Hey, out there - is it *you* reading me, or is it someone else? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message