FreeBSD Security Advisory FreeBSD-SA-06:26.gtar

2006-12-06 Thread FreeBSD Security Advisories
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 = FreeBSD-SA-06:26.gtar Security Advisory The FreeBSD Project Topic:

Re: FreeBSD Security Advisory FreeBSD-SA-06:25.kmem

2006-12-06 Thread Colin Percival
FreeBSD Security Advisories wrote: FreeBSD-SA-06:25.kmem Security Advisory The FreeBSD Project ... III. Impact A user in the operator group can read the contents of kernel memory. Such memory

Re: FreeBSD Security Advisory FreeBSD-SA-06:25.kmem

2006-12-06 Thread Josh Paetzel
On Wednesday 06 December 2006 04:07, Colin Percival wrote: FreeBSD Security Advisories wrote: FreeBSD-SA-06:25.kmem Security Advisory The FreeBSD Project ... III. Impact A user in the operator group can read the contents of kernel memory. Such

Re: FreeBSD Security Advisory FreeBSD-SA-06:25.kmem

2006-12-06 Thread Peter Pentchev
On Wed, Dec 06, 2006 at 02:43:03PM +0100, Ruben de Groot wrote: On Wed, Dec 06, 2006 at 06:26:31AM -0600, Josh Paetzel typed: On Wednesday 06 December 2006 04:07, Colin Percival wrote: FreeBSD Security Advisories wrote: FreeBSD-SA-06:25.kmem

Re: FreeBSD Security Advisory FreeBSD-SA-06:25.kmem

2006-12-06 Thread Dan Lukes
Colin Percival napsal/wrote: A user in the operator group can read the contents of kernel memory. Such memory might contain sensitive information, such as portions of the file cache or terminal buffers. This information might be directly useful, or it might be leveraged to obtain elevated

Re: FreeBSD Security Advisory FreeBSD-SA-06:25.kmem

2006-12-06 Thread Craig Edwards
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Doesn't securelevel completely mitigate this even for root users anyway, if set? Setting securelevel denies raw access to disk devices and kmem in this way does it not? - -- Craig Edwards Dan Lukes wrote: Colin Percival napsal/wrote: A user in the