On Fri, 29 Sep 2017, Jason A. Donenfeld wrote:
> On Fri, Sep 29, 2017 at 12:33 AM, James Morris wrote:
> > Generally speaking, we likely need to improve the amount of crypto review
> > for kernel crypto users including keys (I'll post a note separately to
> > ksummit-discuss).
On Fri, 29 Sep 2017, Jason A. Donenfeld wrote:
> On Fri, Sep 29, 2017 at 12:33 AM, James Morris wrote:
> > Generally speaking, we likely need to improve the amount of crypto review
> > for kernel crypto users including keys (I'll post a note separately to
> > ksummit-discuss).
>
> Indeed.
>
>
On Fri, Sep 29, 2017 at 12:33 AM, James Morris wrote:
> Generally speaking, we likely need to improve the amount of crypto review
> for kernel crypto users including keys (I'll post a note separately to
> ksummit-discuss).
Indeed.
I won't be at kernel summit, regrettably, but
On Fri, Sep 29, 2017 at 12:33 AM, James Morris wrote:
> Generally speaking, we likely need to improve the amount of crypto review
> for kernel crypto users including keys (I'll post a note separately to
> ksummit-discuss).
Indeed.
I won't be at kernel summit, regrettably, but I do intend to
Hi Linus,
Please pull these fixes for the keys subsystem.
Notable here is a rewrite of big_key crypto by Jason Donenfeld to address
some issues in the original code.
>From Jason's commit log:
"This started out as just replacing the use of crypto/rng with
get_random_bytes_wait, so that we
Hi Linus,
Please pull these fixes for the keys subsystem.
Notable here is a rewrite of big_key crypto by Jason Donenfeld to address
some issues in the original code.
>From Jason's commit log:
"This started out as just replacing the use of crypto/rng with
get_random_bytes_wait, so that we
6 matches
Mail list logo