From owner-freebsd-security Wed Nov 17 9:38:14 1999 Delivered-To: freebsd-security@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id A4D231533F for ; Wed, 17 Nov 1999 09:38:00 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id SAA01856; Wed, 17 Nov 1999 18:37:26 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Kelly Yancey Cc: freebsd-security@FreeBSD.ORG Subject: Re: kernel stack contents visible from userland In-reply-to: Your message of "Wed, 17 Nov 1999 12:01:40 EST." Date: Wed, 17 Nov 1999 18:37:26 +0100 Message-ID: <1854.942860246@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message , Kelly Y ancey writes: > > Is there any security concern with a portion of the kernel's stack being >visible from userland? Not as far as I can tell. The kernel stack is per process, and the kernel generally doesn't muck with datastructures until it has checked permissions, so there doesn't seem to be much reason to take the performance overhead of zeroing out stuff. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message