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=78597 --- shadow/78597 2006-08-05 12:23:39.000000000 -0400 +++ shadow/78597.tmp.1437 2006-08-05 12:51:00.000000000 -0400 @@ -522,6 +522,71 @@ (*) I'm not 100% sure about that version, but it's the version I indicated while writing the README from: mcs/class/Mono.Security/Test/tools/npgsql/README Fx/Michael, can you duplicate the problem and/or success ? Thanks + +------- Additional Comments From [EMAIL PROTECTED] 2006-08-05 12:50 ------- + +Hi Sebastien! + +The behavior you are seeing is really strange. + +To me, at least, even with 8.1.4 it is given me the problem I said. I +put the CWL in the Current property added by patch. This is the new +output. + +mono NpgsqlTest.exe +CurrentMonoSecurity <=== CWL added. +PostgreSQL 8.1.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.1.1 +(Gentoo 4.1.1) +PostgreSQL 8.1.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.1.1 +(Gentoo 4.1.1) +PostgreSQL 8.1.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.1.1 +(Gentoo 4.1.1) +PostgreSQL 8.1.4 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 4.1.1 +(Gentoo 4.1.1) +err +Backend sent unrecognized response type: +Successful. + +The problem is that I'm not being able to pass past renegotiation +problem :( + + +LOG: statement: select version(); +LOG: statement: select version(); +LOG: SSL renegotiation failure +LOG: SSL error: ssl handshake failure +LOG: could not send data to client: Connection reset by peer +LOG: SSL error: ssl handshake failure +LOG: could not receive data from client: Connection reset by peer +LOG: unexpected EOF on client connection + + + +But after removing the throw exception from NpgsqlState.cs, I didn't +receive renegotiation problems anymore!!! + +This is very strange.... + +I readded the throw exception in NpgsqlState.cs and I'm receiving +again the renegotiation problem.... + +So, it seems Npgsql may be receiving some empty byte before starting +working again.... + +Can you confirm that, Sebastien? That if you readd the throw +exception, you receive errors? + + +I will keep loop running here to see if I can get this problem again. + +I don't know if the check postgresql does to get a new renegotiation +wasn't meet again. I mean, at first, with only 4, or 5 iterations, it +claimed about renegotiation problems, and now it doesn't. + +I will make more tests and I will try with 8.0.1 to see if I receive +any problems there too. + +Thanks Sebastien. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
