Skip to contentSkip to conversation

TOMOYO in linux-next

DISCUSSION Bodo Eggert 2 participants 7 messages Mar 27, 2009 – Mar 30, 2009 1 message 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]

#1 lore raw
Quoted 2 lines · Pavel Machek

I don't think merging that is good idea. Security should be doable without making shell-like glob matching...

How do you suppose a security system should handle mozilla modifying ~/.bashrc differently from downloading something to ~/pr0n.jpg?

#2 lore raw
Quoted 7 lines · Bodo Eggert
Quoted 2 lines · Pavel Machek

I don't think merging that is good idea. Security should be doable without making shell-like glob matching...

How do you suppose a security system should handle mozilla modifying ~/.bashrc differently from downloading something to ~/pr0n.jpg?

How does shell-like glob matching help there? You'd need to parse /etc/passwd to find all ~ directories...

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#3 lore raw
Quoted 11 lines · Pavel Machek
Quoted 7 lines · Bodo Eggert
Quoted 2 lines · Pavel Machek

I don't think merging that is good idea. Security should be doable without making shell-like glob matching...

How do you suppose a security system should handle mozilla modifying ~/.bashrc differently from downloading something to ~/pr0n.jpg?

How does shell-like glob matching help there? You'd need to parse /etc/passwd to find all ~ directories...

That is, if you'd use HOME=dd if=/dev/urandom ....

If you have your users in /home/user, you can tell /home/*/.* is bad, /home/*/[^.]* is OK.

How would you exclude mozilla from writing to .* then? ".a" is bad, ".b" is bad ...? or "A" is OK, "a" is OK, "zzzzzzzzzzzzz" is OK"? Either way, you'd need several universes to store the security profile.

Signature · 1 line
The enemy diversion you have been ignoring will be the main attack.
#4 lore raw
Quoted 10 lines · Bodo Eggert
Quoted 9 lines · Pavel Machek
Quoted 7 lines · Bodo Eggert
Quoted 2 lines · Pavel Machek

I don't think merging that is good idea. Security should be doable without making shell-like glob matching...

How do you suppose a security system should handle mozilla modifying ~/.bashrc differently from downloading something to ~/pr0n.jpg?

Quoted 7 lines
Quoted 2 lines

How does shell-like glob matching help there? You'd need to parse /etc/passwd to find all ~ directories...

That is, if you'd use HOME=dd if=/dev/urandom ....

If you have your users in /home/user, you can tell /home/*/.* is bad, /home/*/[^.]* is OK.

On the common systems I know of, homes are spread over different volumes and different directories. TOMOYO's wildcards do _not_ solve this particular problems.

Quoted 3 lines

How would you exclude mozilla from writing to .* then? ".a" is bad, ".b" is bad ...? or "A" is OK, "a" is OK, "zzzzzzzzzzzzz" is OK"? Either way, you'd need several universes to store the security profile.

What is magic about .* files? I want mozilla to store the pictures as .naughty.picture.jpg -- I don't see anything wrong with that.
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#5 lore raw
Quoted 14 lines · Pavel Machek
Quoted 13 lines · Bodo Eggert
Quoted 11 lines · Pavel Machek
Quoted 7 lines · Bodo Eggert
Quoted 2 lines · Pavel Machek

I don't think merging that is good idea. Security should be doable without making shell-like glob matching...

How do you suppose a security system should handle mozilla modifying ~/.bashrc differently from downloading something to ~/pr0n.jpg?

How does shell-like glob matching help there? You'd need to parse /etc/passwd to find all ~ directories...

Quoted 8 lines
Quoted 4 lines

That is, if you'd use HOME=dd if=/dev/urandom ....

If you have your users in /home/user, you can tell /home/*/.* is bad, /home/*/[^.]* is OK.

On the common systems I know of, homes are spread over different volumes and different directories. TOMOYO's wildcards do _not_ solve this particular problems.

Don't do that then. If you start having user's homes at /usr/local/sbin/something/, your systenm is FUBAR anyway.

Put your homes into /home/volume/group/user (=~ /home/*/*/*/.*).

Quoted 6 lines
Quoted 3 lines

How would you exclude mozilla from writing to .* then? ".a" is bad, ".b" is bad ...? or "A" is OK, "a" is OK, "zzzzzzzzzzzzz" is OK"? Either way, you'd need several universes to store the security profile.

What is magic about .* files? I want mozilla to store the pictures as .naughty.picture.jpg -- I don't see anything wrong with that.

As long as you have a guaranteed-to-be-complete list of config files, you can get along without wildcards. And still if you do, I'll write a program to make it incomplete.

#6 lore raw
Quoted 11 lines
Quoted 7 lines
Quoted 4 lines

How would you exclude mozilla from writing to .* then? ".a" is bad, ".b" is bad ...? or "A" is OK, "a" is OK, "zzzzzzzzzzzzz" is OK"? Either way, you'd need several universes to store the security profile.

What is magic about .* files? I want mozilla to store the pictures as .naughty.picture.jpg -- I don't see anything wrong with that.

As long as you have a guaranteed-to-be-complete list of config files, you can get along without wildcards. And still if you do, I'll write a program to make it incomplete.

Not all config files match .* pattern. I have at least hugo.ini mxmap.ini in my ~.
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#7 lore raw
Quoted 8 lines · Pavel Machek
Quoted 8 lines
Quoted 7 lines
Quoted 4 lines

How would you exclude mozilla from writing to .* then? ".a" is bad, ".b" is bad ...? or "A" is OK, "a" is OK, "zzzzzzzzzzzzz" is OK"? Either way, you'd need several universes to store the security profile.

What is magic about .* files? I want mozilla to store the pictures as .naughty.picture.jpg -- I don't see anything wrong with that.

Quoted 6 lines
Quoted 3 lines

As long as you have a guaranteed-to-be-complete list of config files, you can get along without wildcards. And still if you do, I'll write a program to make it incomplete.

Not all config files match .* pattern. I have at least hugo.ini mxmap.ini in my ~.

       ^^^^

I see a pattern there.

IMO there is no use in a security system if it allows you to modify something like ~/.bashrc, and a security system not allowing mozilla to create ~/.mozilla or ~/pr0n.jpg is not usable at all.

You must handle different files in one directory diffrerently, and since they are not there yet, you can't label them. Instead, you'll have to label them at runtime, and you have to do it based on the filename. At the same time, you have a HUGE number of problematic filenames and a HUGE number of safe filenames. Unless you have about 500 universes, you can't implement a bitmap of allowed an non-allowed filenames.

What will you do? Give up and let mozilla modify all the config files you didn't think of? Or not let mozilla store tux.png in ~?

Signature · 1 line
Artificial Intelligence usually beats real stupidity.