On 14 Jan 2006 at 15:54, Nicolas MASSE wrote: > > ------- Comment #1 from [EMAIL PROTECTED] 2006-01-14 05:07 PST ------- > > (In reply to comment #0) > > > > > So, I watched my /etc/fstab and found : > > > udev /dev tmpfs nosuid,noexec,size=16M 0 0 > > > > > > After I removed the noexec flag, all worked perfectly. > > > > You are not supposed to have noexec for udev, it doesn't work on multiple > > occasions. > > I think it's my fault because noexec and nosuid are not standard flags for > udev. But I don't understand why it doesn't work...
and in my mind i mixed up /dev with /dev/shm which is noexec by default on gentoo. anyway, making /dev noexec would be good as well, and i'd like to know what else (besides mmap(PROT_EXEC) of /dev/zero) breaks. does anyone have more info? > The man page of mount does'nt mention the bug : > > noexec Do not allow direct execution of any binaries on the mounted > > file system. (Until recently it was possible to run binaries anyway using > > a command like /lib/ld*.so /mnt/binary. This trick fails since > > Linux 2.4.25 / 2.6.0.) 'execution' doesn't mean 'execve', it means 'create an executable file mapping', which is what eventually execve does internally. and the noexec mount enforcement (quite correctly) operates at the mmap level (and with PaX, mprotect as well). so mmap(PROT_EXEC) of any file (including /dev/zero) on a noexec mount will be denied. -- [email protected] mailing list
