[Webkit-unassigned] [Bug 163166] New: [GTK] Certificate database missing when accessing HTTPS via WebKitWebSourceGStreamer

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Sat Oct 8 10:00:40 PDT 2016


https://bugs.webkit.org/show_bug.cgi?id=163166

            Bug ID: 163166
           Summary: [GTK] Certificate database missing when accessing
                    HTTPS via WebKitWebSourceGStreamer
    Classification: Unclassified
           Product: WebKit
           Version: Other
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: Normal
          Priority: P3
         Component: WebKit Gtk
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: jana at saout.de
                CC: bugs-noreply at webkitgtk.org

Using WebkitGtk 2.14.0 (I don't know if this issue is relater to the GStreamer code, WK2 or SOUP interface, but it happens on my WebkitGtk branch, so I picke [GTK]):

A video tag linking to a .m3u8 file (e.g. this one)

https://video.twimg.com/ext_tw_video/783084968578723841/pu/pl/b-QJrB5LSssa0f07.m3u8

will make GStreamer choose the "HLS" plugin, which will try to create a HTTP source to read that particular file.

The gstreamer interface will attach this to WebKitWebSourceGStreamer, which will start the request using libsoup.

However, this always fails with "unacceptable TLS certificate" for me. I did some chasing:

The TLS connection in use doesn't have any certificate database set (i.e. the GObject property "database" of GTlsConnectionGnutls is NULL).

Some debugging output pointed out that for ALL other HTTP connections, there is a non-NULL database set.

Digging further yielded that this HTTP connection is made from the WebKitWebProcess task whereas all other requests are madefromthe WebkitNetworkProcess task.

This is the point where my knowledge ends because I don't know what was supposed to happen here. In case all HTTP traffic is supposed to to through the network process, you have the issue there. If not, the issue might be that the web process doesn't have access to the certificate database.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161008/00e47acd/attachment.html>


More information about the webkit-unassigned mailing list