[Mono-bugs] [Bug 76804][Nor] Changed - WS over HTTPS

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Nov 23 12:01:25 EST 2005

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by sebastien at ximian.com.


--- shadow/76804	2005-11-23 11:33:11.000000000 -0500
+++ shadow/76804.tmp.21722	2005-11-23 12:01:25.000000000 -0500
@@ -1,16 +1,16 @@
 Bug#: 76804
 Product: Mono: Class Libraries
 Version: 1.1
-OS: other
+OS: All
 OS Details: Debian Sarge
-Status: NEW   
+Status: ASSIGNED   
-Priority: Wishlist
-Component: System.Security
+Severity: Unknown
+Priority: Normal
+Component: Mono.Security
 AssignedTo: sebastien at ximian.com                            
 ReportedBy: pere.rodriguez.rodriguez at gmail.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -168,6 +168,25 @@
 Additional Information:
 The development was over HTTP URL, and so I don't have this problem. Now 
 we install the software and we know that over HTTPS ws can't run.
 Thanks you very much.
 I'm sorry, my english is very bad :(.
+------- Additional Comments From sebastien at ximian.com  2005-11-23 12:01 -------
+From a quick look at the certificate it looks like Mono, like Lynx,
+doesn't like the extra informations in the subject name (I must look
+into the HTTPS RFC to be sure about the right behaviour).
+If you need a rapid fix then I suggest you read about
+ICertificatePolicy and implement one that will disregard this specific
+error (for your service) in your client code. This won't affect your
+code portability, will quickly "solve" your problem and, anyway, is a
+good thing to have to properly diagnose errors and report them back to
+the end-users.
+You can get some useful information from
+* http://www.mono-project.com/FAQ:_Security
+* http://www.mono-project.com/UsingTrustedRootsRespectfully
+* the tlstest source code in SVN
+* MSDN...

More information about the mono-bugs mailing list