| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | mark(at)mark(dot)mielke(dot)cc |
| Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Mark Kirkwood <markir(at)paradise(dot)net(dot)nz> |
| Subject: | Re: TODO: GNU TLS |
| Date: | 2006-12-30 18:44:14 |
| Message-ID: | 4596B37E.5020204@hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
mark(at)mark(dot)mielke(dot)cc wrote:
> On Sat, Dec 30, 2006 at 06:05:14PM +0100, Martijn van Oosterhout wrote:
>> Except tht X.509 is already done (in a sense). The client can supply a
>> certificate that the server can check, and vice-versa. You can't link
>> this with the postgresql username yet, but I havn't seen any proposals
>> about how to do that.
>
> I suggest associating the SHA-1 fingerprint with the ROLE. I would love
> to have this.
I would suggest a map based on the CN. Any org with a centralized PKI
infrastructure is likely to assign certs with the userid or other unique
identifier in the CN.
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-12-30 18:44:58 | Re: TODO: GNU TLS |
| Previous Message | Bruce Momjian | 2006-12-30 18:38:59 | Re: TODO: GNU TLS |