Date: Tue, 16 Apr 2019 19:03:35 -0400 From: Ed Maste <emaste@freebsd.org> To: Conrad Meyer <cem@freebsd.org> Cc: Shawn Webb <shawn.webb@hardenedbsd.org>, 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: <CAPyFy2AA00-=evHx%2B-H-TNJY4Yr-zRkvwYHWchiOcfTQutDYSw@mail.gmail.com> In-Reply-To: <CAG6CVpXh1QudAF0RAv2xN62-2-PcJx6xTUzqKYixwg94rtR8Rg@mail.gmail.com> References: <201904160412.x3G4CgN2015092@repo.freebsd.org> <20190416131915.2ocot4nonnf3sl4a@mutt-hbsd> <CAG6CVpXh1QudAF0RAv2xN62-2-PcJx6xTUzqKYixwg94rtR8Rg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 16 Apr 2019 at 11:38, Conrad Meyer <cem@freebsd.org> wrote: > > 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. It's probably worth having tcpdump emit a warning if it's not able to enter capability mode as a result of the options in use, if someone's interested in proposing a patch.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2AA00-=evHx%2B-H-TNJY4Yr-zRkvwYHWchiOcfTQutDYSw>