From: Christian Schoenebeck <qemu_oss@crudebyte.com>
To: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Alexander Graf <agraf@csgraf.de>
Subject: Re: macOS (Big Sur, Apple Silicon) 'make check' fails in test-crypto-tlscredsx509
Date: Wed, 27 Jan 2021 13:35:37 +0100 [thread overview]
Message-ID: <26424319.eypid10iWP@silver> (raw)
In-Reply-To: <20210127121723.GI3653144@redhat.com>
On Mittwoch, 27. Januar 2021 13:17:23 CET Daniel P. Berrangé wrote:
> On Tue, Jan 26, 2021 at 04:41:13PM +0000, Peter Maydell wrote:
> > On Tue, 26 Jan 2021 at 16:37, Daniel P. Berrangé <berrange@redhat.com>
wrote:
> > > On Tue, Jan 26, 2021 at 04:32:08PM +0000, Peter Maydell wrote:
> > > > ** (tests/test-crypto-tlscredsx509:35180): CRITICAL **: 16:23:34.590:
> > > > Failed to sign certificate ASN1 parser: Value is not valid.
> > > > ERROR test-crypto-tlscredsx509 - Bail out! FATAL-CRITICAL: Failed to
> > > > sign certificate ASN1 parser: Value is not valid.
> > > > make: *** [run-test-70] Error 1
> > > >
> > > >
> > > > Does this failure ring any bells for anybody?
> > >
> > > Not seen it before.
> > >
> > > Is this using a gnutls from homebrew, or one that apple
> > > ship themselves ? Any idea what version it is ?
> >
> > Homebrew gnutls, 3.6.15.
>
> On further investigation it seems the error comes from libtasn1,
> but unfortunately there are 100's of scenarios it could arise
> so difficult one to debug.
I haven't looked into the relevant code of this discussion, but is the failing
code dealing with Apple certificates? Because Apple just announced a switch of
one of their intermediate certificates, so just in case this might be related.
Best regards,
Christian Schoenebeck
next prev parent reply other threads:[~2021-01-27 12:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 16:32 macOS (Big Sur, Apple Silicon) 'make check' fails in test-crypto-tlscredsx509 Peter Maydell
2021-01-26 16:36 ` Daniel P. Berrangé
2021-01-26 16:41 ` Peter Maydell
2021-01-27 12:17 ` Daniel P. Berrangé
2021-01-27 12:35 ` Christian Schoenebeck [this message]
2021-01-27 12:38 ` Daniel P. Berrangé
2021-01-27 16:44 ` Stefan Weil
2021-01-27 16:53 ` Daniel P. Berrangé
2021-01-27 17:05 ` Stefan Weil
2021-01-27 18:17 ` Daniel P. Berrangé
2021-01-27 18:56 ` Stefan Weil
2021-01-27 18:59 ` Daniel P. Berrangé
2021-01-27 19:42 ` Stefan Weil
2021-01-27 20:57 ` Stefan Weil
2021-01-29 8:43 ` Roman Bolshakov
2021-01-29 9:53 ` Daniel P. Berrangé
2021-02-02 5:19 ` Roman Bolshakov
2021-02-02 14:19 ` qemu_oss--- via
2021-02-02 14:50 ` Eric Blake
2021-02-02 16:35 ` qemu_oss--- via
2021-02-02 17:14 ` Eric Blake
2021-02-02 20:31 ` Stefan Weil
2021-02-02 20:50 ` Stefan Weil
2021-02-03 10:00 ` Daniel P. Berrangé
2021-02-02 16:50 ` Daniel P. Berrangé
2021-02-03 14:28 ` Roman Bolshakov
2021-02-02 5:46 ` 罗勇刚(Yonggang Luo)
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=26424319.eypid10iWP@silver \
--to=qemu_oss@crudebyte.com \
--cc=agraf@csgraf.de \
--cc=berrange@redhat.com \
--cc=peter.maydell@linaro.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).