Horton

Re: Supporting Windows SChannel as OpenSSL replacement

Jeff Janes <jeff.janes@gmail.com>

View thread View on postgr.es
From: Jeff Janes <jeff.janes@gmail.com>
To: Heikki Linnakangas <hlinnakangas@vmware.com>
Cc: Andreas Karlsson <andreas@proxel.se>, Martijn van Oosterhout <kleptog@svana.org>, Magnus Hagander <magnus@hagander.net>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2014-08-15T17:16:27Z
Lists: pgsql-hackers 
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