@seb128 can you double check my thinking? It looks like the regressions on Bionic with glib-networking/2.56.0-1 are related to newer versions of GnuTLS reporting GNUTLS_CERT_INSECURE_ALGORITHM on the test certificates. Michael Catanzaro posted a patch on 2018-04-11 on comment 3 at: https://bugzilla.gnome.org/show_bug.cgi?id=794286#c3
This fixed test 3/8 certificate after applying the patch, generating the certs (tls/tests/files/create-files.sh) and building the package. Test 4/8 file-database failed with the same error. It looks like tls/tests/files/ca-verisign-sha1.pem was signed with sha1 and also needs to be updated.
I believe this indicates the tests are no longer valid and is unrelated to the changes I made. How do you want to handle this?
@seb128 can you double check my thinking? It looks like the regressions on Bionic with glib-networking /2.56.0- 1 are related to newer versions of GnuTLS reporting GNUTLS_ CERT_INSECURE_ ALGORITHM on the test certificates. Michael Catanzaro posted a patch on 2018-04-11 on comment 3 at: /bugzilla. gnome.org/ show_bug. cgi?id= 794286# c3
https:/
This fixed test 3/8 certificate after applying the patch, generating the certs (tls/tests/ files/create- files.sh) and building the package. Test 4/8 file-database failed with the same error. It looks like tls/tests/ files/ca- verisign- sha1.pem was signed with sha1 and also needs to be updated.
I believe this indicates the tests are no longer valid and is unrelated to the changes I made. How do you want to handle this?