linux-kernel - Re: [PATCH] certs: make system keyring depend on x509 parser

lists.openwall.net		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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 18 Jul 2022 08:55:35 +0200
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Adam Borowski <kilobyte@...band.pl>,
        David Howells <dhowells@...hat.com>,
        David Woodhouse <dwmw2@...radead.org>,
        keyrings@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [PATCH] certs: make system keyring depend on x509 parser

Hi, this is your Linux kernel regression tracker.

Thx for looking into this.

On 18.07.22 01:11, Adam Borowski wrote:
> This code requires x509_load_certificate_list() to be built-in.
> 
> Fixes: 60050ffe3d770dd1df5b641aa48f49d07a54bd84

Just BTW: per docs.kernel.org/process/submitting-patches.html this
should be

Fixes: 60050ffe3d77 ("certs: Move load_certificate_list() to be with the
asymmetric keys code")

But I write for a different reason: Could you also please add "Link:"
and "Reported-by:" tags for earlier reports about this issue please:

Reported-by: kernel test robot <lkp@...el.com>
Link: https://lore.kernel.org/all/202206221515.DqpUuvbQ-lkp@intel.com/
Reported-by: Steven Rostedt <rostedt@...dmis.org>
Link:
https://lore.kernel.org/all/20220712104554.408dbf42@gandalf.local.home/

tia

> […]

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

P.P.S.: Let me tell regzbot to monitor this thread:

#regzbot ^backmonitor:
https://lore.kernel.org/all/20220712104554.408dbf42@gandalf.local.home/