On Wed, Oct 5, 2016 at 8:42 PM, Tom Lane wrote:
> Robert Haas writes:
> > On Wed, Oct 5, 2016 at 5:36 AM, Daniel Gustafsson
> wrote:
> >> The main questions raised here are: is it of interest to support
> multiple SSL
> >> libraries given the additional support burden and; is supporting Secure
Robert Haas writes:
> On Wed, Oct 5, 2016 at 5:36 AM, Daniel Gustafsson wrote:
>> The main questions raised here are: is it of interest to support multiple SSL
>> libraries given the additional support burden and; is supporting Secure
>> Transport of any interest or is it a wasted effort to conti
On Wed, Oct 5, 2016 at 5:36 AM, Daniel Gustafsson wrote:
> The main questions raised here are: is it of interest to support multiple SSL
> libraries given the additional support burden and; is supporting Secure
> Transport of any interest or is it a wasted effort to continue towards a full
> front
> On 05 Oct 2016, at 16:45, Stephen Frost wrote:
>
> Daniel,
>
> * Daniel Gustafsson (dan...@yesql.se) wrote:
>> The main questions raised here are: is it of interest to support multiple SSL
>> libraries given the additional support burden and; is supporting Secure
>> Transport of any interest o
Daniel,
* Daniel Gustafsson (dan...@yesql.se) wrote:
> The main questions raised here are: is it of interest to support multiple SSL
> libraries given the additional support burden and; is supporting Secure
> Transport of any interest or is it a wasted effort to continue towards a full
> frontend/
As noted in 77fb2321-9210-4ad4-b7fc-67623a583...@justatheory.com, OpenSSL is
being somewhat dismantled on macOS starting with 10.11 El Capitan. To scratch
my own itch I decided to take a stab at adding support for the Secure Transport
library. The idea is to make it as much of a drop-in for the O