On Sun, 2005-03-20 at 01:22 +0100, Rene Scharfe wrote:
> The permissions of files in /proc/1 (usually belonging to init) are
> kept as they are. The idea is to let system processes be freely
> visible by anyone, just as before. Especially interesting in this
> regard would be instances of
On Sun, 20 Mar 2005, Rene Scharfe wrote:
> The permissions of files in /proc/1 (usually belonging to init) are
> kept as they are. The idea is to let system processes be freely
> visible by anyone, just as before. Especially interesting in this
> regard would be instances of login.
I think you
The following patches implement another interface that allows an admin
to restrict permissions inside /proc/ to enhance the privacy of
users. Following a suggestion by Albert Calahan this set of patches
introduces five sysctls, each one changes the permissions of a certain
file in /proc/.
It
The following patches implement another interface that allows an admin
to restrict permissions inside /proc/pid to enhance the privacy of
users. Following a suggestion by Albert Calahan this set of patches
introduces five sysctls, each one changes the permissions of a certain
file in /proc/pid.
On Sun, 20 Mar 2005, Rene Scharfe wrote:
The permissions of files in /proc/1 (usually belonging to init) are
kept as they are. The idea is to let system processes be freely
visible by anyone, just as before. Especially interesting in this
regard would be instances of login.
I think you
On Sun, 2005-03-20 at 01:22 +0100, Rene Scharfe wrote:
The permissions of files in /proc/1 (usually belonging to init) are
kept as they are. The idea is to let system processes be freely
visible by anyone, just as before. Especially interesting in this
regard would be instances of login. I
6 matches
Mail list logo
