diff options
| author | Daniel P. Berrangé <berrange@redhat.com> | 2022-03-04 19:35:59 +0000 |
|---|---|---|
| committer | Eric Blake <eblake@redhat.com> | 2022-03-07 15:58:42 -0600 |
| commit | d41997e465c533f3a29e0d0bb52cfcad696e2b2d (patch) | |
| tree | 220816944d36b23a0c4dc5c4b5ccdc0c8e555225 /python/qemu/utils/qom_common.py | |
| parent | b49872aa8fc0f3f5a3036cc37aa2cb5c92866f33 (diff) | |
| download | focaccia-qemu-d41997e465c533f3a29e0d0bb52cfcad696e2b2d.tar.gz focaccia-qemu-d41997e465c533f3a29e0d0bb52cfcad696e2b2d.zip | |
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>
Diffstat (limited to 'python/qemu/utils/qom_common.py')
0 files changed, 0 insertions, 0 deletions