| commit | 057ad0b46992e3ec4ce29b9103162aa3c683f347 | |
| author | Daniel P. Berrangé <berrange@redhat.com> | |
| Wed, 28 Feb 2018 14:04:38 +0000 (28 14:04 +0000) | ||
| committer | Daniel P. Berrangé <berrange@redhat.com> | |
| Fri, 6 Apr 2018 10:28:31 +0000 (6 11:28 +0100) | ||
| tree | bf99c928d0e20fcd4bc145aa44eb3237a2f010c5 | treesnapshot (tar.gz zip) |
| parent | 00e5e9df29453964c724f2156b6fbf32620d8b7e | commitdiff |
crypto: ensure we use a predictable TLS priority setting
The TLS test cert generation relies on a fixed set of algorithms that are
only usable under GNUTLS' default priority setting. When building QEMU
with a custom distro specific priority setting, this can cause the TLS
tests to fail. By forcing the tests to always use "NORMAL" priority we
can make them more robust.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
The TLS test cert generation relies on a fixed set of algorithms that are
only usable under GNUTLS' default priority setting. When building QEMU
with a custom distro specific priority setting, this can cause the TLS
tests to fail. By forcing the tests to always use "NORMAL" priority we
can make them more robust.
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
| tests/test-crypto-tlssession.c | diffblobblamehistory | |
| tests/test-io-channel-tls.c | diffblobblamehistory |