After some more screwing around, I'm not entirely certain windows is
even trying to open my certs. After repeatedly trying to connect it
seemed like I was getting an equal amount of the sslv3 and SSL SYSCALL
errors, whether or not the certs were (where I thought?) windows was
looking for them..
Which leads me to my next question; that function client_cert_cb, does
it ever get executed on windows? :)
I mean, that's the function with the useful error messages (that helped
me on linux), is it not? And the error messages on windows are anything
but useful...and at the beginning of that function there is a:
#ifdef WIN32
return 0;
#else
... (function)
return 1;
#endif
Tom Lane wrote:
>"T.J." <tjtoocool@phreaker.net> writes:
>
>
>>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.
>>
>>
>
>Actually, it asks getpwuid() for the user's home directory,
>rather than looking for an environment variable named HOME.
>See client_cert_cb() in fe-secure.c.
>
>This could probably be documented better, but I'm not sure how.
>The average user is even less likely to be familiar with getpwuid()
>than $HOME, so it doesn't seem like referencing that library function
>is much of an improvement.
>
> regards, tom lane
>
>
>
