Bug#865803: libsoup2.4 FTBFS: Unacceptable TLS certificate

[Simon McVittie]

Control: retitle 865803 libsoup2.4 FTBFS: Unacceptable TLS certificate
Control: tags 865803 + upstream patch fixed-upstream
Control: forwarded 865803 https://bugzilla.gnome.org/show_bug.cgi?id=784949

On Sun, 25 Jun 2017 at 00:49:53 +0300, Adrian Bunk wrote:
> FAIL: misc-test 4 /misc/aliases

This is not very informative. The more interesting part of a recent
Autotools test log is further down, after the heading you quoted:

> ==========================================
>    libsoup 2.56.0: tests/test-suite.log
> ==========================================
> 
> # TOTAL: 526
> # PASS:  461
> # SKIP:  50
> # XFAIL: 0
> # FAIL:  10
> # XPASS: 0
> # ERROR: 5

The bug here seems to be:

**
ERROR:misc-test.c:822:do_aliases_test_for_session: assertion failed (redirect_protocol == redirected_protocol): ("https" == NULL)
**
ERROR:misc-test.c:824:do_aliases_test_for_session: Unexpected status 6 Unacceptable TLS certificate (expected 200 OK)
...
**
ERROR:server-test.c:397:do_multi_test: Unexpected status 6 Unacceptable TLS certificate (expected 200 OK)
**
ERROR:ssl-test.c:21:do_properties_test_for_session: assertion failed (flags == G_TLS_CERTIFICATE_UNKNOWN_CA): (3 == 1)
...
**
ERROR:ssl-test.c:122:do_strictness_test: 'soup_message_get_flags (msg) & SOUP_MESSAGE_CERTIFICATE_TRUSTED' should be TRUE

This seems to be https://bugzilla.gnome.org/show_bug.cgi?id=784949
for which there is a patch. The test certificate in tests/test-cert.pem
was not generated according to modern TLS practices: GNUTLS now wants to
see subjectAltName and SHA256.

    S