linux-kernel - Re: [PATCH] crypto : asymmetric_keys: Fix function description to match prototype

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] [day] [month] [year] [list]

Message-ID: <6f1f6221-6628-5445-cfa9-ae4d7557d33b@infradead.org>
Date:   Wed, 6 Oct 2021 10:45:07 -0700
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Colin King <colin.king@...onical.com>,
        David Howells <dhowells@...hat.com>,
        Herbert Xu <herbert@...dor.apana.org.au>,
        "David S . Miller" <davem@...emloft.net>, keyrings@...r.kernel.org,
        linux-crypto@...r.kernel.org
Cc:     kernel-janitors@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] crypto : asymmetric_keys: Fix function description to
 match prototype

On 10/6/21 10:23 AM, Colin King wrote:
> From: Colin Ian King <colin.king@...onical.com>
> 
> The function arguments in the description does not match the prototype.
> Fix this by renaming trust_keys to trusted_keys.
> 
> Signed-off-by: Colin Ian King <colin.king@...onical.com>
> ---
>   crypto/asymmetric_keys/verify_pefile.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/crypto/asymmetric_keys/verify_pefile.c b/crypto/asymmetric_keys/verify_pefile.c
> index 7553ab18db89..148cad70fe79 100644
> --- a/crypto/asymmetric_keys/verify_pefile.c
> +++ b/crypto/asymmetric_keys/verify_pefile.c
> @@ -387,7 +387,7 @@ static int pefile_digest_pe(const void *pebuf, unsigned int pelen,
>    * verify_pefile_signature - Verify the signature on a PE binary image
>    * @pebuf: Buffer containing the PE binary image
>    * @pelen: Length of the binary image
> - * @trust_keys: Signing certificate(s) to use as starting points
> + * @trusted_keys: Signing certificate(s) to use as starting points
>    * @usage: The use to which the key is being put.
>    *
>    * Validate that the certificate chain inside the PKCS#7 message inside the PE
> 

or this one (which I have sent 2x):
https://lore.kernel.org/all/20211004001731.26240-1-rdunlap@infradead.org/

-- 
~Randy