Skip to contentSkip to conversation

procfs permissions on 2.6.x

DISCUSSION Andi Kleen 3 participants 3 messages Jul 4, 2004 8 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#8 lore raw
Quoted 3 lines · [email protected] writes:

Why on the earth do we ever want to allow chown/chmod on procfs in the first place?

It's useful to stop other people from reading your environment or command line.

-Andi

#9 lore raw
Quoted 7 lines · Andi Kleen
Quoted 3 lines · [email protected] writes:

Why on the earth do we ever want to allow chown/chmod on procfs in the first place?

It's useful to stop other people from reading your environment or command line.

We wouldn't need that feature if mods are accurately defined from the beginning (ie at creation) at that's already the case AFAICS.

FabF

#10 lore raw
Quoted 1 line

if mods are accurately defined from the beginning

Is there a single "accurate" definition (of /proc file permissions) on which we agree? I suspect not.

Signature · 3 lines
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <[email protected]> 1.650.933.1373