| From: | Dev Kumkar <devdas(dot)kumkar(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Heartbleed Impact |
| Date: | 2014-04-16 19:40:58 |
| Message-ID: | CALSLE1PAqV+BechM6dYaxMOSjEqQmfpem64ByWOVuzsG6jgh6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Apr 17, 2014 at 12:53 AM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> windows native stuff uses completely different TLS libraries, SChannel and
> stuff. AFAIK, these aren't subject to this bug, which was specific to
> OpenSSL 1.0.1x for x=a-f... openssl is only used on windows when someone
> uses it explicitly, such as in Cygwin applications, and such.
>
> It *is* used by postgresql under windows as enterpriseDB builds it, since
> PG was written to use openssl in the first place.
>
> --
> john r pierce 37N 122W
> somewhere on the middle of the left coast
So does this mean PostgreSQL binaries available on EnterpriseDB has an
impact for windows ?
Can you help me with the binary name?
Regards...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | yhe | 2014-04-16 19:52:36 | hot standby data folder bigger than primary |
| Previous Message | John R Pierce | 2014-04-16 19:23:11 | Re: Heartbleed Impact |