Date: Tue, 16 Apr 2019 08:37:52 -0700 From: Conrad Meyer <cem@freebsd.org> To: Shawn Webb <shawn.webb@hardenedbsd.org> Cc: src-committers <src-committers@freebsd.org>, svn-src-all <svn-src-all@freebsd.org>, svn-src-head <svn-src-head@freebsd.org> Subject: Re: svn commit: r346263 - head/contrib/tcpdump Message-ID: <CAG6CVpXh1QudAF0RAv2xN62-2-PcJx6xTUzqKYixwg94rtR8Rg@mail.gmail.com> In-Reply-To: <20190416131915.2ocot4nonnf3sl4a@mutt-hbsd> References: <201904160412.x3G4CgN2015092@repo.freebsd.org> <20190416131915.2ocot4nonnf3sl4a@mutt-hbsd>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 16, 2019 at 6:20 AM Shawn Webb <shawn.webb@hardenedbsd.org> wrote: > Is there any documentation anywhere telling users that Capsicum > support will be disabled under certain circumstances? Hi Shawn, I don't think documenting that makes much sense in general. It would be extremely burdensome to fully document and quickly become desynchronized from the code. It's comparable to OpenBSD pledging differently in different paths of programs. To me, "for now," suggests that this is perhaps a temporary workaround and maybe we can do something better in the future. Take care, Conrad P.S., When do you plan to update your Easy Feature Comparison page to reflect that FreeBSD has the same procfs and "boot hardening" as HBSD?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpXh1QudAF0RAv2xN62-2-PcJx6xTUzqKYixwg94rtR8Rg>