Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv.
From: Jacques A. Vidrine (nectar_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."
- In reply to: Ruslan Ermilov: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Next in thread: Tom Rhodes: "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 10:42:27 -0600 To: Ruslan Ermilov <ru@FreeBSD.org>
On Fri, Mar 12, 2004 at 05:46:00PM +0200, Ruslan Ermilov 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
This doesn't seem to contradict anything we've discussed so far, does
it?
> I'm happy with changing our behavior to Strictly Conforming for the
> goods of security, and you?
Isn't that a bonus if it also makes us `Strictly Conforming'? :-)
Cheers,
-- Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org _______________________________________________ freebsd-security@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"
- Previous message: Ruslan Ermilov: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- In reply to: Ruslan Ermilov: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Next in thread: Tom Rhodes: "Re: bin/64150: [PATCH] ls(1) coredumps when started via execve(2) with no argv."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
|
