From: RVK <rvk@prodmail.net>
To: Arjan van de Ven <arjan@infradead.org>
Cc: omb@bluewin.ch, linux-kernel@vger.kernel.org
Subject: Re: Buffer Over-runs, was Open source firewalls
Date: Fri, 15 Jul 2005 14:59:38 +0530 [thread overview]
Message-ID: <42D78202.2040503@prodmail.net> (raw)
In-Reply-To: <1121417215.3179.7.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
>On Fri, 2005-07-15 at 13:56 +0530, RVK wrote:
>
>
>>>except this is no longer true really ;)
>>>
>>>randomisation for example makes this a lot harder to do.
>>>gcc level tricks to prevent buffer overflows are widely in use nowadays
>>>too (FORTIFY_SOURCE and -fstack-protector). The combination of this all
>>>makes it a LOT harder to actually exploit a buffer overflow on, say, a
>>>distribution like Fedora Core 4.
>>>
>>>
>>>
>>>
>>>
>>>
>>Still is very new....not every one can immediately start using gcc 4.
>>
>>
>
>it;s also available for gcc 3.4 as patch (and included in FC3 and RHEL4
>for example)
>
>so it's new? so what? doesn't make it less true that it nowadays is a
>lot harder to exploit such bugs on recent distros.
>
>
Can I get more details on this patch for 3.4. Where can I find it ?
rvk
>.
>
>
>
next prev parent reply other threads:[~2005-07-15 9:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-13 16:34 Open source firewalls Vinay Venkataraghavan
2005-07-13 16:47 ` Alejandro Bonilla
2005-07-13 17:00 ` Maciej Soltysiak
2005-07-13 17:04 ` Nigel Rantor
2005-07-14 10:13 ` Helge Hafting
2005-07-14 10:24 ` RVK
2005-07-14 12:20 ` Helge Hafting
2005-07-14 12:20 ` RVK
2005-07-14 13:06 ` Helge Hafting
2005-07-14 14:04 ` RVK
2005-07-14 22:53 ` Buffer Over-runs, was " Brian O'Mahoney
2005-07-15 6:41 ` RVK
2005-07-15 6:51 ` Arjan van de Ven
2005-07-15 8:26 ` RVK
2005-07-15 8:46 ` Arjan van de Ven
2005-07-15 9:28 ` RVK
2005-07-15 9:29 ` RVK [this message]
2005-07-15 11:17 ` RVK
2005-07-15 11:24 ` Arjan van de Ven
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=42D78202.2040503@prodmail.net \
--to=rvk@prodmail.net \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=omb@bluewin.ch \
/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.