| From: | Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
| Cc: | PostgreSQL <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Changed SSL Certificates |
| Date: | 2011-04-08 20:11:37 |
| Message-ID: | BANLkTimcVMvAxxbejqqYcv+QiEA3yDMaOA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Apr 8, 2011 at 2:01 PM, Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> wrote:
> Per here:
> http://www.postgresql.org/docs/8.4/static/ssl-tcp.html
> File Contents Effect
> server.crt server certificate requested by client
> server.key server private key proves server certificate sent by
> owner; does not indicate certificate owner is trustworthy
> root.crt trusted certificate authorities checks that client
> certificate is signed by a trusted certificate authority
> root.crl certificates revoked by certificate authorities client
> certificate must not be on this list
>
> Rename your certs to above.
Oh I mis-understood. I just need to rename my symbolic links, not my
actual certificate file names. Changed symbolic link names and
everything is happy again.
Thanks so much for everyones help!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2011-04-08 21:27:04 | Re: PostgreSQL backend process high memory usage issue |
| Previous Message | Jerry Sievers | 2011-04-08 19:46:27 | Re: Deferred foreign key constraint downsides |