Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv.

From: Ruslan Ermilov (ru_at_freebsd.org)
Date: 03/15/04

  • Next message: Marc Olzheim: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv." 
    Date: Mon, 15 Mar 2004 22:23:12 +0200
To: Marc Olzheim <marcolz@stack.nl>

    On Mon, Mar 15, 2004 at 01:25:05PM +0100, Marc Olzheim wrote:
    > On Fri, Mar 12, 2004 at 08:29:52PM +0100, Marc Bevand wrote:
    > > On 12 Mar 2004, Ruslan Ermilov wrote:
    > > | On Fri, Mar 12, 2004 at 11:07:25AM -0500, Tom Rhodes wrote:
    > > | >
    > > | > Will it 'break' anything?
    > > |
    > > | Sure it will, the question is should we care about something that's
    > > | already broken. ;)
    > >
    > > It will break almost all shellcodes trying to be the shorter ones
    > > (as they pass NULL for argv and envp). So we can view it as a small
    > > security improvement (just kidding).
    >
    > When I tested my patches (over 2 years ago), I didn't trigger any
    > compilation, nor any runtime problems...
    >
    You didn't try any shellcodes lurking out there, did you? ;)

    Cheers, 

    -- 
Ruslan Ermilov
FreeBSD committer
ru@FreeBSD.org

  • Next message: Marc Olzheim: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."