| From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Dave Page" <dpage(at)postgresql(dot)org>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: OpenSSL Applink |
| Date: | 2007-09-28 16:26:46 |
| Message-ID: | e51f66da0709280926o4d8a4a1cn4148598bea723217@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On 9/28/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dave Page <dpage(at)postgresql(dot)org> writes:
> > Andrew Dunstan wrote:
> >> Then I think I'd rather disable use of client certs for the offending
> >> openssl versions in libpq, or let the apps die and refer the customers
> >> to the openssl people to lobby them for a sane solution.
>
> > If this were 8.0 I'd agree, but thats not a nice solution for those
> > already using client certs (such as the pgAdmin user who brought this to
> > my attention).
>
> Doesn't really matter. Even if we were willing to hack our own client
> apps like that (which I'm not), we can *not* transfer such a requirement
> onto every libpq-using application. It's just not acceptable.
Is it possible to use GNUTLS on Windows?
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2007-09-28 16:30:29 | Re: OpenSSL Applink |
| Previous Message | Dave Page | 2007-09-28 16:26:35 | Re: OpenSSL Applink |