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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=76279 --- shadow/76279 2005-11-15 04:38:15.000000000 -0500 +++ shadow/76279.tmp.11790 2005-12-27 16:23:32.000000000 -0500 @@ -347,6 +347,94 @@ ------- Additional Comments From [EMAIL PROTECTED] 2005-11-15 04:38 ------- Any activity on this?. Do You need more info?. + +------- Additional Comments From [EMAIL PROTECTED] 2005-12-27 16:23 ------- +UPDATE OF RECREATION PROCEDURE (2005-12-27). + + + + +CREATE SELF-SIGNED ROOT CERT, SERVER CERT AND CLIENT CERT. +========================================================== + +See the text document "Certificate Creation-20". + +To observe!: + +- The certificates should be generated with openssl on Linux. + +- This is my 20th version of the cert creation procedure. + The file names, configuration files etc may have an 'X' in there +file names in the abowe document. + This 'X' should be replaced with '20'!. + +- The CN should be replaced by the test client resp test server +machine names!. + +- 2 configuration files are used, 1 for the root and server certs and +1 for the client cert. + +- The root cert have the password 'testing'. + +- The .p12 files have the password 'service'. + + + +CLIENT SOFTWARE. (Win32SslHttpClient20). +======================================== + +The client software (Win32SslHttpClient20.exe) was created and +compiled with CSharpDevelop. + +The name of the Uri and client and server cert is hard-coded in the +source. +Change those parts marked with a "TODO" mark in the code and +recompile. + + + +SERVER SOFTWARE. (mssslserver20). +================================= + +Compile this software with mcs on your Linux server. +The port name that the server listen to is marked with a TODO mark in +the source file. +(Could be changed to correspond with your needs). + +A makefile is attached to this bug report, so You can cut-and-paste +the compiler command. + + + + + + +Steps to reproduce the problem: +=============================== + +1. Create/Dispatch the certificates according to the abowe. + +2. Change the the Win32 client's code's TODO-parts and compile. + (Obs. the Org.Mentalis.Security.dll must be referenced). + +3. Compile the Linux server (cut-and-paste the the makefile): + (Eventually change the port number - See the TODO marked part in +the code). + (Obs. the Mono.Security.dll must be referenced). + +4. Start the server program with: + + $ mono --debug --trace=none mssslserver20.exe server20-cert.p12 +service + +5. Run the client program (Win32SslHttpClient20.exe). + (Obs. the client certificate - client20-cert.p12 - must be in the +Windows certificate store). + +6. Watch the result comming up on the server's screen. + + The error #-2146762486 should show up. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
