On Mon, Sep 9, 2019 at 2:01 PM Nicolas Dechesne
wrote:
> On Mon, Sep 9, 2019 at 10:58 PM Andre McCurdy wrote:
> >
> > On Mon, Sep 9, 2019 at 1:25 PM Nicolas Dechesne
> > wrote:
> > >
> > > If this reasoning is correct that means that kernel signing + external
> > > module is broken. Note that I
On Mon, Sep 9, 2019 at 10:58 PM Andre McCurdy wrote:
>
> On Mon, Sep 9, 2019 at 1:25 PM Nicolas Dechesne
> wrote:
> >
> > If this reasoning is correct that means that kernel signing + external
> > module is broken. Note that I am working out of Thud for now, i am
> > sending this email for now
On Mon, Sep 9, 2019 at 1:25 PM Nicolas Dechesne
wrote:
>
> If this reasoning is correct that means that kernel signing + external
> module is broken. Note that I am working out of Thud for now, i am
> sending this email for now to get some feedback, and will try to
> reproduce without all our
hi,
things are getting worse , my initial problem was only the visible
piece of the iceberg ;)
On Thu, Sep 5, 2019 at 5:42 PM Bruce Ashfield wrote:
>
> On Thu, Sep 5, 2019 at 10:43 AM Nicolas Dechesne
> wrote:
> >
> > hi,
> >
> > I was looking into a build issue today, related to signing an
On Thu, Sep 5, 2019 at 10:43 AM Nicolas Dechesne
wrote:
>
> hi,
>
> I was looking into a build issue today, related to signing an external
> kernel module. My build failed when calling the kernel utility
> sign-file, the error was that libcrypto.so was not found.
>
> Looking a bit more into that,
