From owner-freebsd-security Tue Feb 12 9:31:37 2002 Delivered-To: freebsd-security@freebsd.org Received: from pkl.net (spoon.pkl.net [212.111.57.14]) by hub.freebsd.org (Postfix) with ESMTP id 57D2637B41F for ; Tue, 12 Feb 2002 09:31:28 -0800 (PST) Received: (from rik@localhost) by pkl.net (8.9.3/8.9.3) id RAA22892; Tue, 12 Feb 2002 17:28:26 GMT From: Rik Date: Tue, 12 Feb 2002 17:28:26 +0000 To: Nicolas Rachinsky Cc: freebsd-security@FreeBSD.ORG Subject: Re: Questions regarding the wheel group Message-ID: <20020212172826.GA22312@spoon.pkl.net> References: <20020212021206.3F3AC9EFD3@okeeffe.bestweb.net> <20020212084759.D21643@cartman.private.techsupport.co.uk> <20020212093000.GB35478@pc5.abc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020212093000.GB35478@pc5.abc> User-Agent: Mutt/1.3.25i 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 Tue, Feb 12, 2002 at 10:30:01AM +0100, Nicolas Rachinsky wrote: > Does this mean if all my users have the primary group "users", they > all can read the memory of processes of other users with the primary > group "users"? If you do ls -l /proc/*/mem, and any of those have the same group as you, and have group readability, then you can read them. I assume there's no way of allowing everyone to read a processes memory. Incidentally, some of my /proc/*/mem files are mode 000. Is this a result of mlock(2), or is it a different function/syscall that's done that? -- PGP Key: D2729A3F - Keyserver: wwwkeys.uk.pgp.net - rich at rdrose dot org Key fingerprint = 5EB1 4C63 9FAD D87B 854C 3DED 1408 ED77 D272 9A3F Public key also encoded with outguess on http://rikrose.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message