All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike McCarty <Mike.McCarty@sbcglobal.net>
To: dosemu <linux-msdos@vger.kernel.org>
Subject: Re: cannot map temp file pool
Date: Wed, 20 Sep 2006 12:11:00 -0500	[thread overview]
Message-ID: <45117624.8010404@sbcglobal.net> (raw)
In-Reply-To: <45117479.7040809@my.home>

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!

  reply	other threads:[~2006-09-20 17:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 12:27 cannot map temp file pool Jan Willem Stumpel
2006-09-19 13:24 ` Damyan Ivanov
2006-09-19 15:24   ` Jan Willem Stumpel
2006-09-19 16:21     ` Robert Komar
2006-09-19 16:48     ` Mike McCarty
2006-09-19 18:12       ` Jan Willem Stumpel
2006-09-19 18:34         ` Robert Komar
2006-09-19 19:16           ` Jan Willem Stumpel
2006-09-19 20:17             ` Bart Oldeman
2006-09-19 20:58               ` Mike McCarty
2006-09-19 21:05                 ` Bart Oldeman
2006-09-20  9:56               ` Jan Willem Stumpel
2006-09-20 16:21                 ` Mike McCarty
2006-09-20 17:03                   ` Jan Willem Stumpel
2006-09-20 17:11                     ` Mike McCarty [this message]
2006-09-20 22:06                     ` Claudia Neumann
2006-09-21 11:17                       ` Jan Willem Stumpel
2006-09-21 17:56                         ` Claudia Neumann
2006-09-19 19:15         ` Alain M.
  -- strict thread matches above, loose matches on Subject: below --
2006-09-24 17:37 Stas Sergeev
2006-09-24 20:41 ` Jan Willem Stumpel
2006-09-25  3:45   ` Stas Sergeev
2006-09-25  8:54     ` Jan Willem Stumpel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45117624.8010404@sbcglobal.net \
    --to=mike.mccarty@sbcglobal.net \
    --cc=linux-msdos@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.