Tom Lane wrote:
> "Matthew T. O'Connor" writes:
> > Tom Lane wrote:
> >> Does Windows even have a concept of home directory? What would be a
> >> reasonable equivalent to ~/.postgresql/ ?
>
> > The versions of windows that the port supports (NT4, 2000, 2003, XP) do
> > have home directories.
>
Tom Lane wrote:
OK ... are you supposed to find it out by looking at the environment
vars, or is there another API defined?
I am planning to consolidate the platform dependency into a function
defined like
static bool pqGetHomeDirectory(char *buf, int bufsize)
{
-- O
"Matthew T. O'Connor" writes:
> Tom Lane wrote:
>> Does Windows even have a concept of home directory? What would be a
>> reasonable equivalent to ~/.postgresql/ ?
> The versions of windows that the port supports (NT4, 2000, 2003, XP) do
> have home directories.
OK ... are you supposed to find
Tom Lane wrote:
I wrote:
win32 hackers, anyone know why it's like this?
Looking through the code, it seems that it's because someone thought
that breaking SSL would be easier than replacing the pqGetpwuid() calls
that are used to find out the user's home directory.
Does Windows even have a
I wrote:
> win32 hackers, anyone know why it's like this?
Looking through the code, it seems that it's because someone thought
that breaking SSL would be easier than replacing the pqGetpwuid() calls
that are used to find out the user's home directory.
Does Windows even have a concept of home dire
Yeah I already tried removing the ifdef's...oh BOY was it not happy :'(
Tom Lane wrote:
"T.J." <[EMAIL PROTECTED]> writes:
Which leads me to my next question; that function client_cert_cb, does
it ever get executed on windows? :)
Um. Looks like someone ifdef'd it out :-(. In fact, if yo
"T.J." <[EMAIL PROTECTED]> writes:
> Which leads me to my next question; that function client_cert_cb, does
> it ever get executed on windows? :)
Um. Looks like someone ifdef'd it out :-(. In fact, if you look
through fe-secure.c, you'll see that just about all the SSL code is
ifdef'd out on Wi
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..
"T.J." <[EMAIL PROTECTED]> 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 hom
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
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 re
11 matches
Mail list logo
