Date: Mon, 17 Jul 2017 17:03:05 +0200 From: "Vlad K." <vlad-fbsd@acheronmedia.com> To: freebsd-stable@freebsd.org Subject: Re: stack_guard hardening bsdinstall option in STABLE and 11.1 Message-ID: <54f7e918d4507b50e64ea766b2b04035@acheronmedia.com> In-Reply-To: <20170717141115.GQ16843@FreeBSD.org> References: <f16afd19d4e0be57dc5cef0b68a7edea@acheronmedia.com> <20170717133359.GP16843@FreeBSD.org> <61f79801976fab6770471cd3e2359652@acheronmedia.com> <20170717141115.GQ16843@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2017-07-17 16:11, Glen Barber wrote: > > kib gave feedback on this in an earlier reply (which I missed before > replying myself). > Neither of which answered my questions, I'm sorry. My question was not about stack sizes in 32 or 64 bit installations, nor about the quality of the fix (if I parse the rm libtrh comment correctly). I simply asked if it's safe to assume the sysctl to be an integer in 11.1 (I'm guessing yes looking at the commits to STABLE, but wanted to be sure), and I also asked why wasn't the bsdinstall-er option change MFC'd after 1 day, two weeks ago, whether it's by omission, simply ENOTIME, or something else... -- Vlad K.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54f7e918d4507b50e64ea766b2b04035>