Skip to contentSkip to conversation

Kernelsources writeable for everyone?!

DISCUSSION Bodo Eggert 1 participant 1 message Jun 25, 2006 6 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]

#6 lore raw
Quoted 7 lines · Matthew Frost
Quoted 4 lines · Joshua Hudson

I feel like asking how they initially get set to world-writable. To me it means that the tree that is being tarred up for distribution is world-writible. I sure hope that it is a single-user box.
-

Quoted 5 lines

Yeah. Having said, "Take advice", I'm also curious as to just the why/how of the current configuration and the work patterns that create it. I get the impression that there *is* a reason for it, because if it were just a security issue, I can't see this much resistance to changing it. Sane tar permissions and sensible usage aside.

The reason is the same for which an application SHOULD NOT impose stricter permissions than 0666 without a reasonon open/create: It's supposed to honor the umask, imposing a restriction is none of it's busines.

Signature · 4 lines
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.

http://david.woodhou.se/why-not-spf.html