| From: | David Blewett <david(at)dawninglight(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Seth Robertson <in-pgsql-hackers(at)baka(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Automatic client certificate selection support for libpq v1 |
| Date: | 2009-05-08 16:44:18 |
| Message-ID: | 9d1f8d830905080944m488437f2pe924c46dd41ea0b6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 8, 2009 at 12:10 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Seth Robertson <in-pgsql-hackers(at)baka(dot)org> writes:
>> I had a situation where I needed to connect to multiple postgresql
>> servers in a variety of programs written in a variety of languages,
>> including some which connected to multiple servers at the same time.
>> As some of you might know, you cannot usefully put multiple
>> certificates or keys in the postgresql.crt/.key files.
>
> Hmm, shouldn't we fix *that* rather than inventing a hack like this?
Possibly a la SSH's authorized_keys or known_hosts formats?
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-05-08 17:34:24 | Re: Some 8.4 changes needed according to pg_migrator testing |
| Previous Message | Tom Lane | 2009-05-08 16:10:13 | Re: [PATCH] Automatic client certificate selection support for libpq v1 |