mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Evgeny Polyakov <johnpol@2ka.mipt.ru>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, torvalds@transmeta.com
Subject: Re: [PATCH] this patch add a possibility to add a random offset to the stack on exec.
Date: Thu, 23 Aug 2001 20:56:02 +0400	[thread overview]
Message-ID: <200108231653.f7NGrOl32250@www.2ka.mipt.ru> (raw)
In-Reply-To: <E15ZttT-0003kI-00@the-village.bc.nu>
In-Reply-To: <200108230130.f7N1Uol14698@www.2ka.mipt.ru> <E15ZttT-0003kI-00@the-village.bc.nu>

Hello.

On Thu, 23 Aug 2001 13:47:31 +0100 (BST)
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

>> "Add a possibility to add a random offset to the stack on exec. This
makes
>> it slightly harder to write generic buffer overflows. This doesn't
really
>> give any real security, but it raises the bar for script-kiddies and
it's
>> really cheap."

AC> Its so slight its useless, and the randomness makes it hard to verify
AC> you
AC> fixed a problem. Remember once an exploit appears a box will get
scanned
AC> hundreds of times - someone will get the right offset 8)

You want to tell, that running 2 process one directky after another( like
exploits do),
and esp will be the same, even with random addition? It's impossible.

But i quite understand your position in this question :(.

AC> There is another good reason for offseting stacks within the page -
AC> especially the kernel stacks which is to avoid things like each apache
AC> task sleeping with wait queues on the same cache colour

---
WBR. //s0mbre

      parent reply	other threads:[~2001-08-23 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-23  1:32 Evgeny Polyakov
2001-08-23  8:48 ` David Weinehall
2001-08-25 14:13   ` Mark H. Wood
2001-08-23 12:47 ` Alan Cox
2001-08-23 16:56 ` Evgeny Polyakov [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=200108231653.f7NGrOl32250@www.2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    /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®