Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<blockquote> <p>SSL connection with unsigned certificate</p> </blockquote> <p>I suspect you're using a <strong>self-signed</strong> (not an <strong>unsigned</strong>) certificate that you made yourself (e.g. <code>makecert</code>) for temporary use.</p> <p>Like others said in comments, this should work as <strong>many</strong> people are doing similar things when developing their applications.</p> <blockquote> <p>It seems like he's ignoring the <code>ServerCertificateValidationCallback</code> and failing somwhere. Is there any way to fix this?</p> </blockquote> <p>Mono (and MonoTouch) supports both the <code>ServerCertificateValidationCallback</code> and the older <code>ICertificatePolicy</code> methods to allow application to have the <em>last</em> word on accepting (or refusing) an X.509 certificate. You can try the other method - but I'm not sure that's the issue.</p> <p>You can also compare your (full, not partial) stack trace with the same code where <code>ServerCertificateValidationCallback</code> is commented. If the error is <strong>identical</strong> then it's likely certificate related, otherwise it's not (there's a lot more that can go wrong with SSL/TLS ;-)</p> <p>Sadly I can't give you more specific help because your question lacks important details.</p> <ul> <li><p>What version of MonoTouch are you using ?</p></li> <li><p>The full stack trace of the exception MonoTouch gives you ? from the partial one you gave it's not 100% clear that the issue happens when certificates are validated.</p></li> <li><p>Where/how did you execute your sample code ? e.g. was it on Mono or Microsoft .NET ? which version ?</p></li> </ul> <p>I suggest you to open a bug report on <a href="http://bugzilla.xamarin.com" rel="nofollow">http://bugzilla.xamarin.com</a> (and include the missing details) since it's likely that we'll require even more data (e.g. a <a href="http://www.wireshark.org/" rel="nofollow">wireshark</a> log of the SSL communication).</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload