For some reason this morning it's working fine and not even falling into
the "changed during execution" error. Maybe it was just windows being
its charming self, since I didn't modify anything since last night.
Either way, I'd say it's working.
> Okay, I've been up all night testing this out and here's what I've got...
> I sprinkled some printf's in fe-secure.c because a different error
> starting coming up...
> I discovered that on an initial connection open_client_SSL was
> attempted 4 times. r is -1 three times, then 0 the fourth time. The
> first three times err is 2, the last time err is 1.
> SSL Initialization isn't entered until the third try. But it works
> fine, the homedir, usercertfile and userkeyfile are identified
> correctly (c:\Documents and Settings\User\ApplicationData/postgresql,
> postgresql.crt, postgresql.key, respectively)
> The error coming up states that the private key file was changed
> during execution. I looked at it (the error checker) and it has
> something to do with comparing two buffers...
> Anyways, after figuring out what was going on I went into that error
> function and commented out the return 0, recompiled and a successful
> SSL connection was made :)
> Good work guys, you rock. =)
>> I'm out of here myself too, it's getting pretty late. Patches too late
>> in the evening tend to need reversal in the morning...:-)
>> But it seems to be working so far - at least as good as it did with RC3.
>> If someone can test the client certificate stuff (that didn't work
>> before), that'd be great.
In response to
pgsql-hackers-win32 by date
|Next:||From: Tom Lane||Date: 2005-01-07 16:03:50|
|Subject: Re: [BUGS] More SSL questions.. |
|Previous:||From: Magnus Hagander||Date: 2005-01-07 15:43:01|
|Subject: Re: PostgreSQL 8 win32 native confilct with Cygwin?|