On Feb 14, 2013, at 4:45 PM, Nikola wrote:
> I think what is needed here is an ability to somehow override the default
> implementation of SSL handshake to be able to sign those random bytes in a
> custom way
I'm told by the resident SSL expert (not me!) that
HttpWebRequest.ClientCertificates
On Feb 14, 2013, at 4:00 PM, Jonathan Pryor wrote:
> I'll provide that code in a bit; if that doesn't help you, let's see about
> getting a full repro...
Bwa-ha-ha-ha-ha-ah-ha *cough* *splutter*
Firstly, the links I previously provided have been invalidated due to
refactoring (yay). That'll te
> This is very helpful context. Thank you. :-)
You are welcome :) Glad that it helped to bring my point across, with
English being my second language I sometimes wonder if my mails are clear
enough.
> Obvious question: Why do you need to use the KeyChain API? Why not just
> include your client c
On Feb 14, 2013, at 3:20 PM, Nikola wrote:
> This is not what I want to achieve. What am I trying to do here is, I
> believe, "officially" called Mutual SSL authentication.
...
> I am pretty sure you are already familiar with how the SSL handshake works
> :), I just want to be absolutely positiv
Jon,
> Using the .NET networking stack and using the
> ServicePointManager.ServerCertificateValidationCallback callback allows me
> to connect to a site which uses a self-signed certificate
This is not what I want to achieve. What am I trying to do here is, I
believe, "officially" called Mutual S
On Feb 8, 2013, at 7:41 AM, Nikola wrote:
> I've tried to use HttpsUrlConnection
> (http://androidapi.xamarin.com/?link=T%3aJavax.Net.Ssl.HttpsURLConnection)
> instead, but unfortunately, I am getting very similar results.
Unfortunately, I cannot use your code as-is, as it's missing crucial con
