From: David Howells <dhowells@redhat.com>
To: Lukas Wunner <lukas@wunner.de>
Cc: dhowells@redhat.com, Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Ignat Korchagin <ignat@cloudflare.com>,
Stefan Berger <stefanb@linux.ibm.com>,
Tadeusz Struk <tstruk@gmail.com>,
Tadeusz Struk <tstruk@gigaio.com>,
Vitaly Chikunov <vt@altlinux.org>,
linux-crypto@vger.kernel.org, keyrings@vger.kernel.org,
Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] MAINTAINERS: Add Lukas & Ignat & Stefan for asymmetric keys
Date: Thu, 06 Mar 2025 07:05:33 +0000 [thread overview]
Message-ID: <666.1741244733@warthog.procyon.org.uk> (raw)
In-Reply-To: <90c171d5beed08bcf65ec2df6357a7ac97520b91.1741194399.git.lukas@wunner.de>
Lukas Wunner <lukas@wunner.de> wrote:
> Herbert asks for long-term maintenance of everything under
> crypto/asymmetric_keys/ and associated algorithms (ECDSA, GOST, RSA) [1].
>
> Ignat has kindly agreed to co-maintain this with me going forward.
>
> Stefan has agreed to be added as reviewer for ECDSA. He introduced it
> in 2021 and has been meticulously providing reviews for 3rd party
> patches anyway.
>
> Retain David Howells' maintainer entry until he explicitly requests to
> be removed. He originally introduced asymmetric keys in 2012.
>
> RSA was introduced by Tadeusz Struk as an employee of Intel in 2015,
> but he's changed jobs and last contributed to the implementation in 2016.
>
> GOST was introduced by Vitaly Chikunov as an employee of Basealt LLC [2]
> (Базальт СПО [3]) in 2019. This company is an OFAC sanctioned entity
> [4][5], which makes employees ineligible as maintainer [6]. It's not
> clear if Vitaly is still working for Basealt, he did not immediately
> respond to my e-mail. Since knowledge and use of GOST algorithms is
> relatively limited outside the Russian Federation, assign "Odd fixes"
> status for now.
>
> [1] https://lore.kernel.org/r/Z8QNJqQKhyyft_gz@gondor.apana.org.au/
> [2] https://prohoster.info/ru/blog/novosti-interneta/reliz-yadra-linux-5-2
> [3] https://www.basealt.ru/
> [4] https://ofac.treasury.gov/recent-actions/20240823
> [5] https://sanctionssearch.ofac.treas.gov/Details.aspx?id=50178
> [6] https://lore.kernel.org/r/7ee74c1b5b589619a13c6318c9fbd0d6ac7c334a.camel@HansenPartnership.com/
>
> Signed-off-by: Lukas Wunner <lukas@wunner.de>
Seems reasonable. Unfortunately, I find myself a bit strapped for time.
Signed-off-by: David Howells <dhowells@redhat.com>
next prev parent reply other threads:[~2025-03-06 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 17:14 [PATCH] MAINTAINERS: Add Lukas & Ignat & Stefan for asymmetric keys Lukas Wunner
2025-03-05 18:54 ` Stefan Berger
2025-03-06 0:46 ` Herbert Xu
2025-03-06 7:05 ` David Howells [this message]
2025-03-06 21:43 ` Jarkko Sakkinen
2025-03-06 22:38 ` Ignat Korchagin
2025-03-15 9:13 ` Herbert Xu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=666.1741244733@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=ignat@cloudflare.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=stefanb@linux.ibm.com \
--cc=tstruk@gigaio.com \
--cc=tstruk@gmail.com \
--cc=vt@altlinux.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox