From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "T(dot)J(dot)" <tjtoocool(at)phreaker(dot)net> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: More SSL questions.. |
Date: | 2005-01-04 00:17:58 |
Message-ID: | 200501040017.j040Hw804799@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers-win32 |
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
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | T.J. | 2005-01-04 06:38:34 | Re: BUG #1369: RC3 Compilation fails on mingw |
Previous Message | jan pfaler | 2005-01-03 21:16:35 | Re: rule-system revaluates the functionale expressions |
From | Date | Subject | |
---|---|---|---|
Next Message | T.J. | 2005-01-04 06:41:52 | Re: More SSL questions.. |
Previous Message | Merlin Moncure | 2005-01-03 20:32:28 | possible bug in case comparison on index scan. |