Twice now you've asserted without warrant that some unexpected FAT
behavior is a security issue. It isn't. It's a "if you don't know what
you're doing, you can fuck up really bad" issue, but not a security one.
Now I grant that a confusing scheme like this is probably bad... I think
we agree there. I think that long names should be the only ones available
in a vfat-mounted fs, and that short names should only be used to fail
creation of other files by that name. But the reason isn't security.
It's principle of least surprise, consistency, and five million other
things.
If you can present a security issue here... a way that an intruder could
exploit that situation to cause root to accidentally delete files (barring
of course, an intruder with root access who coulda done it anyway) that
I'll eat my words and agree that there's a security issue there. Until
then, you are just confusing the matter.
Chris Smith <cd_smith@ou.edu>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/