Not to my knowledge. By the way, for future reference on windows it looks for the cert/key in the linux equivalent of `pwd`/.postgresql/postgresql.crt/key, instead of $HOME/.postgresql/postgresql.crt/key. Maybe you already knew this but I had to do testing to figure it out so hopefully that bit of knowledge will be of use to someone else :)

I tried looking through the source myself for the cause of this problem but I guess there's a reason my perl is so sharp and c so rusty these days..

Don't know if it makes much difference but I have built with vcwin and mingw with the same resulting error.

Bruce Momjian wrote:

Did we ever find the solution to this, or did anyone find the cause?

---------------------------------------------------------------------------

T.J. wrote:


Having some problems (still, hehe) getting SSL to work properly on windows in the new 8.0 (all vers) environment (where cert/key is required).

On the client side when not finding the certificate/key psql would report the SSL error sslv3 alert handshale failure. After I figured out where psql was looking for the files and placing them there I now get the error: SSL SYSCALL error: Connection reset by peer (0x00002746/10054). On the server side it still reports that the peer did not return a certificate.

I am able to connect to the server just fine using the same certificate/key on a linux machine...so I'm guessing it's just another good ol' windows issue? :)


---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?

              http://archives.postgresql.org









---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])

Reply via email to