(Apologies to cem@ for the duplicate in his inbox, Gmail decided to not
reply-all in my reply.)
On Wed, Jun 20, 2018 at 1:07 PM, Conrad Meyer wrote:
> Hi Jon,
>
> On Wed, Jun 20, 2018 at 11:58 AM, Jonathan Anderson
> wrote:
> > On 20 Jun 2018, at 15:32, Jonathan T. Looney wrote:
> >> My
On Wed, Jun 20, 2018 at 9:30 AM, Conrad Meyer wrote:
>
> Please look at the actual code size and layout of the sha1 support
> module and tell me that is a burden for Juniper to maintain in their
> downstream tree, rather than just getting angry about the suggestion
> we don't introduce novel,
On Tue, Jun 19, 2018 at 11:21 PM, Simon J. Gerraty wrote:
> Conrad Meyer wrote:
>
> > As a corollary to the above, the name "signature file" is used
> > repeatedly in the code, which is misleading. The file contains hashes
> > (digests), not signatures (MACs). The file itself is unsigned.
> >
On Wed, Jun 20, 2018, 6:42 AM Cy Schubert wrote:
> In message <96021.1529475...@kaos.jnpr.net>, "Simon J. Gerraty" writes:
> > Conrad Meyer wrote:
> > > First and foremost: nothing is actually signed, anywhere. The
> >
> > The signing of manifests is external. The veriexecctl tool is I assume
On Wed, Jun 20, 2018 at 10:36 PM, Eitan Adler wrote:
> On 19 June 2018 at 20:08, Eitan Adler wrote:
> > On 19 June 2018 at 18:08, Stephen J. Kiernan wrote:
> >> Added: head/sbin/veriexecctl/Makefile
> >>
> ==
> >> ---
