<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">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:<br>
<pre> 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);
</pre>
<br>
Cheers<br>
-Matt<br>
<br>
On 18/06/18 18:42, Kiran ND wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+GETXFDDJpTT+s-VBuwUKY4tcOxH4HeLn4LO0_ZtDoQLx+daA@mail.gmail.com">
<div dir="ltr">Hi.,
<div><br>
</div>
<div><span
style="font-size:12.8px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">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.<br>
</span>>> I have disabled ssl-strict checking in
soup_session_new_with options(), still it doesnt help me much.<br>
<pre style="background-color:rgb(43,43,43);color:rgb(169,183,198);font-family:Menlo;font-size:9pt">session = soup_session_new_with_options (<span style="color:rgb(144,139,37)">SOUP_SESSION_SSL_STRICT</span><span style="color:rgb(204,120,50)">, </span><span style="color:rgb(144,139,37)">FALSE</span><span style="color:rgb(204,120,50)">,
</span><span style="color:rgb(204,120,50)"> </span><span style="color:rgb(144,139,37)">SOUP_SESSION_SSL_USE_SYSTEM_CA_FILE</span><span style="color:rgb(204,120,50)">, </span><span style="color:rgb(144,139,37)">TRUE</span><span style="color:rgb(204,120,50)">,
</span><span style="color:rgb(204,120,50)"> </span><span style="color:rgb(128,128,128)">//SOUP_SESSION_SSL_CA_FILE, "/etc/ssl/certs/ca-bundle.crt",
</span><span style="color:rgb(128,128,128)"> </span><span style="color:rgb(144,139,37)">SOUP_SESSION_HTTPS_ALIASES</span><span style="color:rgb(204,120,50)">, </span>https_aliases<span style="color:rgb(204,120,50)">, </span><span style="color:rgb(144,139,37)">NULL</span>)<span style="color:rgb(204,120,50)">;</span></pre>
<span
style="font-size:12.8px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">As
of a few hours ago, there's a new option for this on both
the</span><br
style="font-size:12.8px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">
<span
style="font-size:12.8px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">client
and the server.</span><br
class="gmail-Apple-interchange-newline">
>> What's the new option that is available?</div>
<div><br>
</div>
<div>Thank you.</div>
<div><br>
</div>
<div>Regards,</div>
<div>Kiran</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Mon, Jun 18, 2018 at 1:27 PM,
Nirbheek Chauhan <span dir="ltr"><<a
href="mailto:nirbheek.chauhan@gmail.com" target="_blank"
moz-do-not-send="true">nirbheek.chauhan@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class="">On Mon, Jun 18, 2018 at 1:13 PM Matthew Waters
<<a href="mailto:ystreet00@gmail.com"
moz-do-not-send="true">ystreet00@gmail.com</a>>
wrote:<br>
><br>
> 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.<br>
><br>
<br>
</span>As of a few hours ago, there's a new option for this
on both the<br>
client and the server.<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>