|From:||Chapman Flack <chap(at)anastigmatix(dot)net>|
|To:||Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: what can go in root.crt ?|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On 05/25/20 23:22, Laurenz Albe wrote:
> I don't know if there is a way to get this to work, but the
> fundamental problem seems that you have got the system wrong.
> If you don't trust WE ISSUE TO EVERYBODY, then you shouldn't use
> it as a certification authority.
That's a reasonable viewpoint.
I've worked in organizations from smallish to largish, and in the
largish ones, sometimes there are Ways Of Doing Things, that were
laid down by Other People.
There the challenge becomes how to piece together practices that
maximize my comfort level, within the ways of doing things that
come down from others.
If the libpq root.crt file can be made to work similarly to a
Java trustStore, that expands the possible solution space.
|Next Message||Isaac Morland||2020-05-26 04:07:23||Re: what can go in root.crt ?|
|Previous Message||Bruce Momjian||2020-05-26 03:36:32||Re: what can go in root.crt ?|