From: Kevin Wolf <kwolf@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [PATCH v2] crypto: use a stronger private key for tests
Date: Thu, 16 Jul 2020 15:33:48 +0200 [thread overview]
Message-ID: <20200716133348.GB4498@linux.fritz.box> (raw)
In-Reply-To: <20200715154701.1041325-1-berrange@redhat.com>
Am 15.07.2020 um 17:47 hat Daniel P. Berrangé geschrieben:
> The unit tests using the x509 crypto functionality have started
> failing in Fedora 33 rawhide with a message like
>
> The certificate uses an insecure algorithm
>
> This is result of Fedora changes to support strong crypto [1]. RSA
> with 1024 bit key is viewed as legacy and thus insecure. Generate
> a new private key which is 3072 bits long and reasonable future
> proof.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2020-07-16 13:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 15:47 [PATCH v2] crypto: use a stronger private key for tests Daniel P. Berrangé
2020-07-15 16:08 ` Philippe Mathieu-Daudé
2020-07-15 16:39 ` Daniel P. Berrangé
2020-07-16 8:20 ` Kashyap Chamarthy
2020-07-16 13:33 ` Kevin Wolf [this message]
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=20200716133348.GB4498@linux.fritz.box \
--to=kwolf@redhat.com \
--cc=berrange@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).