[WebRTC android application]

[Matthew Waters]

In my musings with android, I also had to use the set of bundled
ca-certificates that the GStreamer ndk-build machinery installs into the
application like so:

  ca_certs = g_getenv("CA_CERTIFICATES");
  g_assert (ca_certs != NULL);
  g_print ("ca-certificates %s", ca_certs);
  session = soup_session_new_with_options (SOUP_SESSION_SSL_STRICT, FALSE,
          //                                 SOUP_SESSION_SSL_USE_SYSTEM_CA_FILE, TRUE,
                                           SOUP_SESSION_SSL_CA_FILE, ca_certs,
                                           SOUP_SESSION_HTTPS_ALIASES, https_aliases, NULL);


Cheers
-Matt

On 18/06/18 18:42, Kiran ND wrote:
> Hi.,
>
> This error usually means either you don't have certificates installed
> correctly inside your app or you're attempting to access a server that
> doesn't support https/wss and has the necessary certificates setup. 
> You can get around this either installing the necessary ssl
> certificate chain for your webrtc signalling server or disabling the
> ssl-strict checking in the soup_session_new() function call.
> >> I have disabled ssl-strict checking in soup_session_new_with
> options(), still it doesnt help me much.
> session = soup_session_new_with_options (SOUP_SESSION_SSL_STRICT, FALSE, SOUP_SESSION_SSL_USE_SYSTEM_CA_FILE,
> TRUE, //SOUP_SESSION_SSL_CA_FILE, "/etc/ssl/certs/ca-bundle.crt",
> SOUP_SESSION_HTTPS_ALIASES, https_aliases, NULL);
> As of a few hours ago, there's a new option for this on both the
> client and the server.
> >> What's the new option that is available?
>
> Thank you.
>
> Regards,
> Kiran
>
> On Mon, Jun 18, 2018 at 1:27 PM, Nirbheek Chauhan
> <nirbheek.chauhan at gmail.com <mailto:nirbheek.chauhan at gmail.com>> wrote:
>
>     On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters
>     <ystreet00 at gmail.com <mailto:ystreet00 at gmail.com>> wrote:
>     >
>     > This error usually means either you don't have certificates
>     installed correctly inside your app or you're attempting to access
>     a server that doesn't support https/wss and has the necessary
>     certificates setup.  You can get around this either installing the
>     necessary ssl certificate chain for your webrtc signalling server
>     or disabling the ssl-strict checking in the soup_session_new()
>     function call.
>     >
>
>     As of a few hours ago, there's a new option for this on both the
>     client and the server.
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20180618/7bd08450/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20180618/7bd08450/attachment-0001.sig>