mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Boszormenyi Zoltan <zboszor@freemail.hu>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Gabor MICSKO <gmicsko@szintezis.hu>
Subject: Re: [patch] exec-shield-2.6.0-test6-G3
Date: Sat, 11 Oct 2003 10:04:48 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.56.0310111002270.4993@earth> (raw)
In-Reply-To: <3F854C13.3010902@freemail.hu>


On Thu, 9 Oct 2003, Boszormenyi Zoltan wrote:

> I tried exec-shield-2.6.0-test6-G3 on 2.6.0-test7 patched with
> http://www.kernel.org/pub/linux/kernel/v2.6/testing/cset/cset-20031009_0504.txt.gz
> (up to cset-1.1320), it patched with some fuzz and offset differences.

i've uploaded a clean patch against 2.6.0-test7:

        redhat.com/~mingo/exec-shield/exec-shield-2.6.0-test7-G3

> I got the following exploit differences with libsafe and paxtest:
> 
> libsafe-2.0-16:
> [zozo@catv-50624ad9 exploits]$ ./t6
> This program tries to use scanf() to overflow the buffer.
> If you get a /bin/sh prompt, then the exploit has worked.
> Press any key to continue...
> If you see this statement, it means that the buffer
> overflow never occurred.
> 
> Should I worry about it?

i wouldnt worry about this too much - i think the exploit preparation code
itself crashes sometimes (maybe due to randomization effects). I've seen
it previously too.

	Ingo

  parent reply	other threads:[~2003-10-11  8:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-29  9:11 Boszormenyi Zoltan
2003-09-29  9:23 ` Ingo Molnar
2003-09-30 14:57 ` Ingo Molnar
2003-10-09 11:52   ` Boszormenyi Zoltan
2003-10-09 12:23     ` Arjan van de Ven
2003-10-11  7:51       ` Ingo Molnar
2003-10-11  8:04     ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-29  9:45 Boszormenyi Zoltan
2003-09-29  9:49 ` Ingo Molnar
2003-09-29 10:24   ` Boszormenyi Zoltan
2003-09-28 14:57 Gabor MICSKO
2003-09-28 16:01 ` Ingo Molnar

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=Pine.LNX.4.56.0310111002270.4993@earth \
    --to=mingo@elte.hu \
    --cc=gmicsko@szintezis.hu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zboszor@freemail.hu \
    /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

all inboxes | Powered by JetHome®