| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
| Subject: | Re: SSL connections |
| Date: | 2011-10-04 20:16:00 |
| Message-ID: | CA+OCxowKthxH8mBWiDB4VPxrXHhp8JYnnh+1rryg9hYoyDqBvQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgadmin-hackers |
On Tue, Oct 4, 2011 at 9:12 PM, Guillaume Lelarge
<guillaume(at)lelarge(dot)info> wrote:
> Hi,
>
> One of my customer told me that another PostgreSQL admin tool requires
> to enter sslcert, sslkey, sslrootcert, and sslcrl to try an SSL
> connection. Is this true? do we have to require that all fields are
> filled? reading the documentation, I think no. There are default values
> for each of them, so we don't need to put each field in the connection
> packet. But I may be wrong. Anyone with more knowledge than me on this
> issue?
No you don't need to fill them in to use SSL. Even certificate based
auth doesn't *require* you to set any of those values.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guillaume Lelarge | 2011-10-04 20:19:22 | Re: SSL connections |
| Previous Message | Guillaume Lelarge | 2011-10-04 20:12:14 | SSL connections |