Re: Supporting Windows SChannel as OpenSSL replacement

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Martijn van Oosterhout <kleptog(at)svana(dot)org>, Andreas Karlsson <andreas(at)proxel(dot)se>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Supporting Windows SChannel as OpenSSL replacement
Date: 2014-06-09 17:46:51
Message-ID: CABUevEwk+AmnJfFQC_4mrdDJYNo1uEkTtdS0PZf_Yexq196j9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 9, 2014 at 7:45 PM, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
wrote:

> On 06/09/2014 06:03 PM, Magnus Hagander wrote:
>
>> One tricky part is that programs like to use libpq for the
>>
>>> >authentication, and then they hijack the connection using PGgetssl().
>>> >
>>>
>> Is there*anybody* other than odbc that does that? Do we actually need a
>>
>> published API for that, or just a hack for pgodbc?
>>
>
> I wish psqlODBC would stop doing that. It's kind of cool that it supports
> compiling without libpq, but it's really quite a mess. I think we should
> modify psqlODBC to use the libpq API like most people do.

This was, I believe, done at one point, and then reverted. I think that was
because libpq didn't actually have all the features required either for the
current or for planned featues of the ODBC driver. That situation might be
very different now though, there's more functionality available in libpq..

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2014-06-09 18:14:33 Re: updated emacs configuration
Previous Message Heikki Linnakangas 2014-06-09 17:45:18 Re: Supporting Windows SChannel as OpenSSL replacement