Date: Thu, 21 Jun 2018 11:13:58 -0700 From: Conrad Meyer <cem@freebsd.org> To: Stephen Kiernan <hackagadget@gmail.com> Cc: Eitan Adler <lists@eitanadler.com>, src-committers <src-committers@freebsd.org>, svn-src-all@freebsd.org, svn-src-head@freebsd.org Subject: Re: svn commit: r335402 - head/sbin/veriexecctl Message-ID: <CAG6CVpXAVvxLNQX%2BHWZ50-U4AcHeL0ADYViLzZMXyyJ02TDddQ@mail.gmail.com> In-Reply-To: <CAEm%2B2uUfBefgHWW4WRxbS0KYSnk1FY_j28H9pTOGWhp4GoSREw@mail.gmail.com> References: <201806200108.w5K18sIR050132@repo.freebsd.org> <CAF6rxgkNFfLUZYrjX45p-33C7qZEFMVURSd5w0Z0wBA=vAvTNQ@mail.gmail.com> <CAF6rxgmoi=sEoQyHYr=E8syBgX7au%2BvMmk34L-VfG_sZOMeTyg@mail.gmail.com> <CAEm%2B2uUfBefgHWW4WRxbS0KYSnk1FY_j28H9pTOGWhp4GoSREw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jun 21, 2018 at 9:51 AM, Stephen Kiernan <hackagadget@gmail.com> wrote: > On Wed, Jun 20, 2018 at 10:36 PM, Eitan Adler <lists@eitanadler.com> wrote: >> >> On 19 June 2018 at 20:08, Eitan Adler <lists@eitanadler.com> wrote: >> > On 19 June 2018 at 18:08, Stephen J. Kiernan <stevek@freebsd.org> wrote: >> >> Added: head/sbin/veriexecctl/Makefile >> >> >> >> ============================================================================== >> >> --- /dev/null 00:00:00 1970 (empty, because file is newly added) >> >> +++ head/sbin/veriexecctl/Makefile Wed Jun 20 01:08:54 2018 >> >> (r335402) >> >> @@ -0,0 +1,11 @@ >> >> +# $FreeBSD$ >> >> + >> >> +PROG= veriexecctl >> >> +MAN= veriexecctl.8 >> >> +SRCS= veriexecctl_parse.y veriexecctl_conf.l veriexecctl.c >> >> + >> >> +WARNS?= 3 >> > >> > Why are we introducing new code with lower-than-6 warnings ? >> >> In all the commotion about the more important issues this fell >> through. Also its argument parsing appears to not be using >> getopt[_long] ? > > > I replied to this 2 days ago with: > "veriexecctl came from NetBSD originally and that is what they had, > but I believe it should be able to be bumped up." > > However, there has been some discussion about just not putting in > veriexecctl for now and wait for some work that Simon Gerraty has been > doing, using some of the work for the verified loader, instead. However, it > would also mean that in the meantime, there would be nothing available > to be able to people to try out veriexec to provide some feedback until > that utility was completed and committed. Hi, While the code is out of HEAD, it can be posted to a github branch (or a projects/ branch if you prefer SVN) for people to try. Best regards, Conrad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpXAVvxLNQX%2BHWZ50-U4AcHeL0ADYViLzZMXyyJ02TDddQ>