What steps will reproduce the problem?
1. Connect to a host with DNS name that is different from the name in the cert.
I think two things are neccessary here, namely:
A. A method of pausing socket handling until the user has indicated
acceptance or rejection of the different name situation.
B. A means of configuring the socket at runtime to ignore Commoon Name
mismatches.
I've already added an "IgnoreCNMismatch" value to my tree, but I haven't
yet added an event chain to get information back to my root application
regarding the mismatch. Once I get some time, I'll handle that.
Original issue reported on code.google.com by sh0rtw...@gmail.com on 22 Sep 2008 at 2:47
Original issue reported on code.google.com by
sh0rtw...@gmail.com
on 22 Sep 2008 at 2:47