| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Martin Pitt <mpitt(at)debian(dot)org>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: libpq 8.4 beta1: $PGHOST complains about missing root.crt |
| Date: | 2009-04-10 17:31:31 |
| Message-ID: | 26017.1239384691@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Tom Lane wrote:
>> In my experience ssh itself isn't this strict. Why should libpq be?
> ssh prompts the user when this happens. We don't have a mechanism for
> prompting the user.
In the first place, I have never seen such a prompt, despite the fact
that I use ssh constantly to connect to machines that I know do not have
properly signed certificates. If there is such a prompt, it isn't the
default behavior. In the second place, unconditionally failing isn't a
particularly nice emulation of a prompting behavior.
Perhaps a suitable compromise is to have the failure message include
a hint about how to prevent the failure if you don't want it?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2009-04-10 17:34:59 | Re: libpq 8.4 beta1: $PGHOST complains about missing root.crt |
| Previous Message | Magnus Hagander | 2009-04-10 17:21:57 | Re: libpq 8.4 beta1: $PGHOST complains about missing root.crt |