qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Stefan Weil <sw@weilnetz.de>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Alexander Graf <agraf@csgraf.de>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: macOS (Big Sur, Apple Silicon) 'make check' fails in test-crypto-tlscredsx509
Date: Wed, 27 Jan 2021 18:59:17 +0000	[thread overview]
Message-ID: <20210127185917.GB3653144@redhat.com> (raw)
In-Reply-To: <27c01eba-ebc1-9b8e-d7ea-38ad9b4350d9@weilnetz.de>

On Wed, Jan 27, 2021 at 07:56:16PM +0100, Stefan Weil wrote:
> Am 27.01.21 um 19:17 schrieb Daniel P. Berrangé:
> 
> > On Wed, Jan 27, 2021 at 06:05:08PM +0100, Stefan Weil wrote:
> > > Am 27.01.21 um 17:53 schrieb Daniel P. Berrangé:
> > > 
> > > > In $QEMU.git/crypto/init.c can you uncomment the "#define DEBUG_GNUTLS"
> > > > line and then re-build and re-run the test case.
> > > > 
> > > > There's a bunch of debug logs in code paths from gnutls_x509_crt_privkey_sign
> > > > that might give us useful info.
> > > > 
> > > > Regards,
> > > > Daniel
> > > 
> > > % LANG=C.UTF-8 tests/test-crypto-tlscredsx509
> > > # random seed: R02S9b95072a368ad370cdd4c780b8074596
> > > 3: ASSERT: mpi.c[wrap_nettle_mpi_print]:60
> > > 3: ASSERT: mpi.c[wrap_nettle_mpi_print]:60
> > > 2: signing structure using RSA-SHA256
> > > 3: ASSERT: common.c[_gnutls_x509_der_encode]:855
> > > 3: ASSERT: sign.c[_gnutls_x509_pkix_sign]:174
> > > 3: ASSERT: x509_write.c[gnutls_x509_crt_privkey_sign]:1834
> > > 3: ASSERT: x509_write.c[gnutls_x509_crt_sign2]:1152
> > > Bail out! FATAL-CRITICAL: Failed to sign certificate ASN1 parser: Value is
> > > not valid.
> > So it shows its failing inside a asn1_der_coding call, but I can't see
> > why it would fail, especially if the same test suite passes fine on
> > macOS x86_64 hosts.
> 
> 
> It returns ASN1_MEM_ERROR, so the input vector is too small.

Hmm, that's odd - "Value is not valid" corresponds to
ASN1_VALUE_NOT_VALID error code.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2021-01-27 19:02 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
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é [this message]
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=20210127185917.GB3653144@redhat.com \
    --to=berrange@redhat.com \
    --cc=agraf@csgraf.de \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sw@weilnetz.de \
    /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).