Date: Wed, 20 Jun 2018 08:09:58 -0700 From: "Simon J. Gerraty" <sjg@juniper.net> To: <cem@freebsd.org>, "Stephen J. Kiernan" <stevek@freebsd.org>, src-committers <src-committers@freebsd.org>, <svn-src-all@freebsd.org>, <svn-src-head@freebsd.org>, <sjg@juniper.net> Subject: Re: svn commit: r335402 - head/sbin/veriexecctl Message-ID: <16106.1529507398@kaos.jnpr.net> In-Reply-To: <96021.1529475664@kaos.jnpr.net> References: <201806200108.w5K18sIR050132@repo.freebsd.org> <CAG6CVpV124ze%2BY6xX2ZFqbM%2B3hJNEJWR2qpnChpey=PmiW6qXg@mail.gmail.com> <96021.1529475664@kaos.jnpr.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Simon J. Gerraty <sjg@juniper.net> wrote: > > - Maybe sign the source-of-trust file > > We do. As noted above, we cannot upstream that until FreeBSD has > suitable signing infra. It occurred to me, that since I'll be upstreaming a library that uses BearSSL to do the necessary manifest verification for the loader, the same could be leveraged for the veriexec loader. That may impact where the two libs should go - will discuss with imp.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16106.1529507398>