migration: fix use of TLS PSK credentials with a UNIX socket
The migration TLS code has a check mandating that a hostname be available when starting a TLS session. This is expected when using x509 credentials, but is bogus for PSK and anonymous credentials as neither involve hostname validation. The TLS crdentials object gained suitable error reporting in the case of TLS with x509 credentials, so there is no longer any need for the migration code to do its own (incorrect) validation. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Message-Id: <20220310171821.3724080-7-berrange@redhat.com> Reviewed-by: Juan Quintela <quintela@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
This commit is contained in:
parent
0c2b6c85c9
commit
4b2bbca7a0
@ -137,10 +137,6 @@ QIOChannelTLS *migration_tls_client_create(MigrationState *s,
|
||||
if (s->parameters.tls_hostname && *s->parameters.tls_hostname) {
|
||||
hostname = s->parameters.tls_hostname;
|
||||
}
|
||||
if (!hostname) {
|
||||
error_setg(errp, "No hostname available for TLS");
|
||||
return NULL;
|
||||
}
|
||||
|
||||
tioc = qio_channel_tls_new_client(
|
||||
ioc, creds, hostname, errp);
|
||||
|
Loading…
Reference in New Issue
Block a user