Postgres Pro
Downloads
Home   >   mailing lists

Re: Supporting Windows SChannel as OpenSSL replacement - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Supporting Windows SChannel as OpenSSL replacement
Date
Msg-id CAMkU=1yu+3sdKeemHkcns_PrVwDhN6BOAEy9Qq4A7P-yB6HACg@mail.gmail.com
Whole thread Raw
In response to Re: Supporting Windows SChannel as OpenSSL replacement  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Supporting Windows SChannel as OpenSSL replacement
List pgsql-hackers
Tree view
On Tue, Aug 12, 2014 at 10:52 AM, Heikki Linnakangas <hlinnakangas@vmware.com> wrote:
On 08/06/2014 08:37 PM, Jeff Janes wrote:
But now it looks like 0002 needs a rebase....

I've committed the refactoring patch, and here's a rebased and improved version of the Windows SChannel implementation over that.

On MinGW, I get the following error when compiling with options --host=x86_64-w64-mingw32 --without-zlib:

be-secure.c: In function 'secure_open_server':
be-secure.c:106:2: error: 'Port' has no member named 'peer_cn'
be-secure.c:106:2: error: 'Port' has no member named 'peer_cn'
make[3]: *** [be-secure.o] Error 1
make[2]: *** [libpq-recursive] Error 2
make[1]: *** [all-backend-recurse] Error 2
make: *** [all-src-recurse] Error 2

Should the ereport DEBUG2 be inside the "#ifdef USE_SSL"?

Thanks,

Jeff

pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: Another logical decoding assertion failure
Next
From: Heikki Linnakangas
Date:
Subject: Re: Minmax indexes