| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Self-signed certificate instructions |
| Date: | 2017-04-17 19:43:09 |
| Message-ID: | 29796.1492458189@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I think the reason we have those cumbersome instructions is that there
> is no way to create a non-expireable certificate using simpler
> instructions.
Um ... but the current instructions don't address that either.
> I would like to revisit these instructions, as well as document how to
> create intermediate certificates. I have scripts that do that.
I don't think we should try to teach people how to use openssl.
A quick example of setting up a dummy certificate for testing is fine,
but going much beyond that is not our turf.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-04-17 19:51:01 | Re: Row Level Security UPDATE Confusion |
| Previous Message | Stephen Frost | 2017-04-17 19:41:25 | Re: pg_dump emits ALTER TABLE ONLY partitioned_table |