2 ms·
I cannot repro. See this transcript: http://pastebin.com/y958QtWh http://pastebin.com/y958QtWh By the way: $ man mount MOUNT(8) Syste
by simoncion 12y ago
I cannot repro. See this transcript:
http://pastebin.com/y958QtWh http://pastebin.com/y958QtWh
By the way:
$ man mount
MOUNT(8) System Administration MOUNT(8)
NAME
mount - mount a filesystem
SYNOPSIS
<snip>
defaults
Use default options: rw, suid, dev, exec, auto, nouser, and async.
<snip>
- mhogomchungu 12y agoIts because you overrode the default option of "suid" with your "nosuid" when mounting.TrueCrypt does not do this and that is where the problem is. To reproduce the problem,use TrueCrypt with its default mount options,or do your mounting with mount's default options. The fundamental problem is a bad usage of mount command that comes from usage of mount's default options.You cant reproduce the problem because you changed a bad default option to a good one.
- simoncion 12y ago> The fundamental problem is ... mount's default options. This is exactly my point. You might as well complain to Ted Ts'o about the same vulnerability in ext4. Please do reply to my comment here: https://news.ycombinator.com/item?id=8060884 https://news.ycombinator.com/item?id=8060884