Jan Willem Stumpel wrote:
Mike McCarty wrote:
GREAT! But, why did it fail in the first place?
The immediate reason has been pointed out by Bart. A change in the
[snip]
One of the "initscripts" is /etc/init.d/mountdevsubfs.sh, which
contains line like
(version 15, does not break dosemu)
SHM_OPT=
[ "${SHM_SIZE:=$TMPFS_SIZE}" ] && SHM_OPT="-osize=$SHM_SIZE"
domount tmpfs shmfs /dev/shm $SHM_OPT
("improved" version 20, breaks dosemu)
SHM_OPT=
[ "${SHM_SIZE:=$TMPFS_SIZE}" ] && SHM_OPT=",size=$SHM_SIZE"
domount tmpfs shmfs /dev/shm -onoexec,nosuid,nodev$SHM_OPT
Ah, I see. Very clear.
This must have been done for security reasons, although I have no
clue about (the severity of) the security issues which are at
stake here.
[snip]
Hmm. Self-modifying code permitting one to insert code into
a shared memory region and execute it? Difficult to catch
with a "scanner" I suppose.
Thanks for the response.
Mike
--
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
