|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Sat, 21 Oct 1995 13:14:02 -0700 From: "Leonard N. Zubkoff" <lnz@dandelion.com> To: okir@monad.swb.de Cc: linux-security@tarsier.cv.nrao.edu In-Reply-To: <m0t6joz-00005KC@monad.swb.de> (okir@monad.swb.de) From: okir@monad.swb.de (Olaf Kirch) Date: Sat, 21 Oct 1995 20:43:09 +0100 (MET) Hi Leonard, > and here are the results of a mount command: > > /dev/sr1 on /cd2 type iso9660 (ro,noexec,nosuid,nodev,unhide) > /dev/sr2 on /cd3 type iso9660 (ro,noexec,nosuid,nodev,unhide) > /dev/sr3 on /cd4 type iso9660 (ro,noexec,nosuid,nodev,unhide) > > It sure looks to me like it's working. But the point is whether nosuid is honored by the kernel. The mount command simply copies the options from fstab into mtab, so what the above mount invocation shows is that the options were indeed copied correctly, no more. If you find the time, can you please check what happens if you invoke a setuid program on your cdrom and post the results to the list? I currently don't have a cd drive at home. <sigh> You are indeed correct. The noexec option *is* honored but the nosuid option is not. I've briefly perused the kernel source but I don't see why this should be the case. Leonard
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |