Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv.
From: Ruslan Ermilov (ru_at_FreeBSD.org)
Date: 03/12/04
- Previous message: Ruslan Ermilov: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Maybe in reply to: Ruslan Ermilov: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Next in thread: Marc Bevand: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Reply: Marc Bevand: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Fri, 12 Mar 2004 18:10:49 +0200 To: Tom Rhodes <trhodes@FreeBSD.org>
On Fri, Mar 12, 2004 at 11:07:25AM -0500, Tom Rhodes wrote:
> On Fri, 12 Mar 2004 17:46:00 +0200 Ruslan Ermilov <ru@freebsd.org> wrote:
[...]
> > As Garrett already pointed out in the PR log, have you considered this?
> >
> > http://www.opengroup.org/onlinepubs/007904975/functions/execve.html#tag_03_130_08
> >
> > I'm happy with changing our behavior to Strictly Conforming for the
> > goods of security, and you?
>
> Will it 'break' anything?
>
Sure it will, the question is should we care about something that's
already broken. ;)
Cheers,
-- Ruslan Ermilov FreeBSD committer ru@FreeBSD.org
- application/pgp-signature attachment: stored
- Previous message: Ruslan Ermilov: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Maybe in reply to: Ruslan Ermilov: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Next in thread: Marc Bevand: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Reply: Marc Bevand: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]