Daniel P. Berrangé d41997e465 crypto: mandate a hostname when checking x509 creds on a client ... Currently the TLS session object assumes that the caller will always provide a hostname when using x509 creds on a client endpoint. This relies on the caller to detect and report an error if the user has configured QEMU with x509 credentials on a UNIX socket. The migration code has such a check, but it is too broad, reporting an error when the user has configured QEMU with PSK credentials on a UNIX socket, where hostnames are irrelevant. Putting the check into the TLS session object credentials validation code ensures we report errors in only the scenario that matters. Reviewed-by: Eric Blake <eblake@redhat.com> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Message-Id: <20220304193610.3293146-2-berrange@redhat.com> Signed-off-by: Eric Blake <eblake@redhat.com>		2022-03-07 15:58:42 -06:00
..
aes.c
afalg.c
afalgpriv.h
afsplit.c
block-luks.c
block-luks.h
block-qcow.c
block-qcow.h
block.c
blockpriv.h
cipher-afalg.c
cipher-builtin.c.inc
cipher-gcrypt.c.inc
cipher-gnutls.c.inc
cipher-nettle.c.inc
cipher.c
cipherpriv.h
hash-afalg.c
hash-gcrypt.c
hash-glib.c
hash-gnutls.c
hash-nettle.c
hash.c
hashpriv.h
hmac-gcrypt.c
hmac-glib.c
hmac-gnutls.c
hmac-nettle.c
hmac.c
hmacpriv.h
init.c
ivgen-essiv.c
ivgen-essiv.h
ivgen-plain64.c
ivgen-plain64.h
ivgen-plain.c
ivgen-plain.h
ivgen.c
ivgenpriv.h
meson.build
pbkdf-gcrypt.c
pbkdf-gnutls.c
pbkdf-nettle.c
pbkdf-stub.c
pbkdf.c
random-gcrypt.c
random-gnutls.c
random-none.c
random-platform.c
secret_common.c
secret_keyring.c
secret.c
tls-cipher-suites.c
tlscreds.c
tlscredsanon.c
tlscredspriv.h
tlscredspsk.c
tlscredsx509.c
tlssession.c
trace-events
trace.h
xts.c