All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Eduardo Habkost <eduardo@habkost.net>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PULL 00/13] Next crypto & I/O patches
Date: Fri, 24 Oct 2025 16:38:29 +0100	[thread overview]
Message-ID: <aPuddawJ9Zug9g4D@redhat.com> (raw)
In-Reply-To: <20251024131937.56673-1-berrange@redhat.com>

Self-NACK

I've discovered this fails on CFI enabled builds, because
gnutls_malloc/gnutls_free are incompatible with CFI due
to requiring bad function pointer casts. Fortunately
gnutls 3.3.0 dropped support for replacing the system
allocators, so we can assume C library malloc/free are
acceptable, just as with glib.

I'll post a v2 PULL shortly.


On Fri, Oct 24, 2025 at 02:19:24PM +0100, Daniel P. Berrangé wrote:
> The following changes since commit e8779f3d1509cd07620c6166a9a280376e01ff2f:
> 
>   Merge tag 'pull-riscv-to-apply-20251024' of https://github.com/alistair23/qemu into staging (2025-10-24 10:53:02 +0200)
> 
> are available in the Git repository at:
> 
>   https://gitlab.com/berrange/qemu tags/next-pr-pull-request
> 
> for you to fetch changes up to 608be310a9c0a8501480a8ba76de3df8feaaf0d8:
> 
>   crypto: switch to newer gnutls API for distinguished name (2025-10-24 13:06:05 +0100)
> 
> ----------------------------------------------------------------
> Merge misc, crypto and I/O subsystems changes
> 
>  * Fix use after free in websocket handshake (CVE-2025-11234)
>  * Improved stack traces fatal errors/aborts raised for
>    user creatable objects
>  * Stop requiring 'key encipherment' usage in x509 certs
>  * Only sanity check CA certs needed in the chain of trust
>  * Allow intermediate CA certs to be present in client/server
>    cert file
>  * Fix regression propagating errors in premature shutdown
>    of TLS connections
> 
> ----------------------------------------------------------------
> 
> Daniel P. Berrangé (11):
>   crypto: propagate Error object on premature termination
>   qom: use ERRP_GUARD in user_creatable_complete
>   tests: use macros for registering char tests for sockets
>   io: release active GSource in TLS channel finalizer
>   io: move websock resource release to close method
>   io: fix use after free in websocket handshake code
>   crypto: remove extraneous pointer usage in gnutls certs
>   crypto: validate an error is reported in test expected fails
>   crypto: fix error reporting in cert chain checks
>   crypto: stop requiring "key encipherment" usage in x509 certs
>   crypto: switch to newer gnutls API for distinguished name
> 
> Henry Kleynhans (1):
>   crypto: only verify CA certs in chain of trust
> 
> matoro (1):
>   crypto: allow client/server cert chains
> 
>  crypto/tlscredsx509.c                 | 223 +++++++++++++++-----------
>  crypto/tlssession.c                   |  20 +--
>  docs/system/tls.rst                   |  13 +-
>  include/io/channel-websock.h          |   3 +-
>  io/channel-tls.c                      |  23 ++-
>  io/channel-websock.c                  |  33 +++-
>  qom/object_interfaces.c               |   7 +-
>  tests/unit/crypto-tls-x509-helpers.h  |   6 +-
>  tests/unit/test-char.c                |   8 +-
>  tests/unit/test-crypto-tlscredsx509.c | 155 +++++++++++++++---
>  tests/unit/test-crypto-tlssession.c   |  14 +-
>  tests/unit/test-io-channel-tls.c      |   4 +-
>  12 files changed, 336 insertions(+), 173 deletions(-)
> 
> -- 
> 2.50.1
> 

With 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 :|



      parent reply	other threads:[~2025-10-24 15:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-24 13:19 [PULL 00/13] Next crypto & I/O patches Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 01/13] crypto: propagate Error object on premature termination Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 02/13] qom: use ERRP_GUARD in user_creatable_complete Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 03/13] tests: use macros for registering char tests for sockets Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 04/13] io: release active GSource in TLS channel finalizer Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 05/13] io: move websock resource release to close method Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 06/13] io: fix use after free in websocket handshake code Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 07/13] crypto: only verify CA certs in chain of trust Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 08/13] crypto: remove extraneous pointer usage in gnutls certs Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 09/13] crypto: validate an error is reported in test expected fails Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 10/13] crypto: fix error reporting in cert chain checks Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 11/13] crypto: allow client/server cert chains Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 12/13] crypto: stop requiring "key encipherment" usage in x509 certs Daniel P. Berrangé
2025-10-27 10:20   ` Daniel P. Berrangé
2025-10-24 13:19 ` [PULL 13/13] crypto: switch to newer gnutls API for distinguished name Daniel P. Berrangé
2025-10-24 15:38 ` Daniel P. Berrangé [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=aPuddawJ9Zug9g4D@redhat.com \
    --to=berrange@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=pbonzini@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.