| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
| Cc: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "T(dot)J(dot)" <tjtoocool(at)phreaker(dot)net>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers-win32(at)postgresql(dot)org |
| Subject: | Re: [pgsql-hackers-win32] More SSL questions.. |
| Date: | 2005-01-05 21:44:12 |
| Message-ID: | 1330.1104961452@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers-win32 |
"Magnus Hagander" <mha(at)sollentuna(dot)net> writes:
> I think it's only broken when you fiddle with certificates.
Yeah, the commented-out stuff had to do with certificates, and would not
be executed unless the server demands a client certificate (which only
happens if the server has a root.crt file).
BTW, as of CVS tip, if the server has a root.crt file and the client
does not have any certificate files, the default behavior is that
connections fail:
$ psql -h localhost regression
psql: could not open certificate file "/home/tgl/.postgresql/postgresql.crt": No such file or directory
$
I'm not sure if this is desirable. Should libpq try to fall back to a
non-SSL-encrypted connection, instead?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-01-05 22:20:19 | Re: [pgsql-hackers-win32] More SSL questions.. |
| Previous Message | Magnus Hagander | 2005-01-05 21:37:42 | Re: [pgsql-hackers-win32] More SSL questions.. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-01-05 22:20:19 | Re: [pgsql-hackers-win32] More SSL questions.. |
| Previous Message | Magnus Hagander | 2005-01-05 21:41:30 | Re: [BUGS] More SSL questions.. |