| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martin Pitt <mpitt(at)debian(dot)org> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: libpq 8.4 beta1: $PGHOST complains about missing root.crt |
| Date: | 2009-04-10 23:01:52 |
| Message-ID: | 3084.1239404512@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Martin Pitt <mpitt(at)debian(dot)org> writes:
> The reason why Debian/Ubuntu install a snakeoil SSL certificate and
> configure all packages to use it by default is not because we think
> that this default configuration is "secure" in any way. The reason is
> that configuring it that way is that it becomes darn easy to make your
> entire server with all daemons such as postgresql, postfix, dovecot,
> etc. trusted by simply replacing that central certificate. You can
> still configure individual services to use a different one.
This seems a bit handwavy --- there's a difference between the machine's
own cert and what it thinks is a root cert. How do you deal with that?
If the root cert is real, how do you put in self-signed server certs?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Pitt | 2009-04-10 23:15:20 | Re: libpq 8.4 beta1: $PGHOST complains about missing root.crt |
| Previous Message | Martin Pitt | 2009-04-10 22:57:46 | Re: libpq 8.4 beta1: $PGHOST complains about missing root.crt |