From: Joel Soete <joel.soete@tiscali.be>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthew Wilcox <willy@debian.org>,
Ruediger Scholz <rscholz@hrzpub.tu-darmstadt.de>,
parisc-linux@lists.parisc-linux.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [parisc-linux] Security Hole in binfmt_som.c ?
Date: Mon, 01 Sep 2003 08:00:34 +0000 [thread overview]
Message-ID: <3F52FCA2.5050500@tiscali.be> (raw)
In-Reply-To: <1062251389.31150.4.camel@dhcp23.swansea.linux.org.uk>
Alan Cox wrote:
>On Sad, 2003-08-30 at 14:15, Matthew Wilcox wrote:
>
>
>>On Sat, Aug 30, 2003 at 02:42:37PM +0200, Ruediger Scholz wrote:
>>
>>
>>>binfmt_som.c:216:2: #error "Fix security hole before enabling me"
>>>What's this message about?
>>>
>>>
>>I don't know. I wish someone would tell me. You'd think they'd have the
>>decency to contact the person listed as the author at the top of the file.
>>
>>
>
>Actually explanations were posted in the previous discussion on this on
>parisc-list.
>
>Someone has to do the equivalent of the 2.4.22 binfmt_elf changes if
>neccessary so that another thread can't change the file handles or
>steal the exec fd being passed to the loader.
>
>
>
Yes Alan, it was:
<http://lists.parisc-linux.org/pipermail/parisc-linux/2003-July/020386.html>
Sorry Willy I trusted that you read it (My bad next time I will advise
you directly)
Joel
prev parent reply other threads:[~2003-09-01 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F509BBD.2040007@hrzpub.tu-darmstadt.de>
2003-08-30 13:15 ` [parisc-linux] Security Hole in binfmt_som.c ? Matthew Wilcox
2003-08-30 13:49 ` Alan Cox
2003-08-30 13:59 ` Matthew Wilcox
2003-08-30 23:33 ` Alan Cox
2003-09-01 8:00 ` Joel Soete [this message]
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=3F52FCA2.5050500@tiscali.be \
--to=joel.soete@tiscali.be \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rscholz@hrzpub.tu-darmstadt.de \
--cc=willy@debian.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox