From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Andrew M <andrew(at)jibeya(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: PostgreSQL + SSL - sun.security.validator.ValidatorException |
Date: | 2004-12-11 20:13:34 |
Message-ID: | Pine.BSO.4.56.0412111509490.404@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Sat, 11 Dec 2004, Andrew M wrote:
> so the best I can do at the moment, in terms of ssl on postgresql via
> JDBC, is to use an unauthenticated connection!? Is man in the middle a
> real concern, as the data in the tables will be encrypted?
No, it's not unauthenticed. We authenticate the server certificate, but
not a client certificate. This is exactly like browsing to a https
website. You validate the server's certificate, checking that they are
who they say they are, but you don't send the web server a client
certificate. This means the web server, or in our case the postgresql
server, cannot verify that you are who you say are from the ssl connection
alone, but there are other means of doing this, like a password.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Oliver Jowett | 2004-12-11 22:54:59 | Re: PostgreSQL + SSL - sun.security.validator.ValidatorException |
Previous Message | Tom Lane | 2004-12-11 18:27:21 | Re: [JDBC] Issue with large objects |