Date: Fri, 10 Mar 2023 21:39:22 +0000 From: Brooks Davis <brooks@freebsd.org> To: Lucy Marsh <seafork@disroot.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Adding the secure_getenv call to FreeBSD's libc Message-ID: <ZAujisiQgadg/R4d@spindle.one-eyed-alien.net> In-Reply-To: <64fc1989-aa35-7a5f-fc0a-bc649b68ecee@disroot.org> References: <64fc1989-aa35-7a5f-fc0a-bc649b68ecee@disroot.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 10, 2023 at 04:27:05PM -0500, Lucy Marsh wrote: > Dear FreeBSD Hackers, >=20 > I was wondering if adding the glibc extension call, `secure_getenv`, to= =20 > FreeBSD's libc is allowed. Obviously, this would not only need to be=20 > permitted but also wanted. In that latter department, I could see the=20 > need arise for `secure_getenv` when porting applications written for=20 > Linux as they are often written targeting glibc. Also, this addition=20 > would bring us more inline with other libc implementations such as musl= =20 > libc. Looking at the musl implementation, it looks like this is part of a set of environment (mostly path) hardening changes in libc. On the whole they seem like reasonable things to do if we haven't already done them on an adhoc basis. -- Brooks
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ZAujisiQgadg/R4d>