lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Thu, 14 Jan 2021 06:15:24 +0200
From:   Jarkko Sakkinen <>
To:     Mickaël Salaün <>
Cc:     David Howells <>,
        David Woodhouse <>,
        "David S . Miller" <>,
        Herbert Xu <>,
        James Morris <>,
        Mickaël Salaün <>,
        Mimi Zohar <>,
        "Serge E . Hallyn" <>,,,,,
Subject: Re: [PATCH v2 0/5] Enable root to update the blacklist keyring

On Sun, Jan 10, 2021 at 06:57:10AM +0200, Jarkko Sakkinen wrote:
> On Tue, Jan 05, 2021 at 11:12:57AM +0100, Mickaël Salaün wrote:
> > Jarkko, David, what is the status of this patch series? Do you need help
> > to test it?
> Hi, a leave/vacation and the holiday period badly mixed my schedules.
> I'm testing this upcoming week.
> /Jarkko

❯ git-pw series apply 400795
Applying: certs: Make blacklist_vet_description() more strict
error: sha1 information is lacking or useless (certs/blacklist.c).
error: could not build fake ancestor
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 certs: Make blacklist_vet_description() more strict
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

Can you rebase to rc3 and resend? 

Also, please add this to the patches 1-3:

Acked-by: Jarkko Sakkinen <>

Also, 4-5 look good but I hold for testing before acking further.

Thanks, and apologies for such a long wait.


Powered by blists - more mailing lists