ssl client cert authentication
ssl client cert authentication
От:
Ray Stell <stellr@cns.vt.edu>
Дата:
Someone asked about ssl client cert auth recently. I got this to work, but something tripped me up. http://developer.postgresql.org/pgdocs/postgres/ssl-tcp.html states (very clearly, btw) that, "To require the client to supply a trusted certificate, place certificates of the certificate authorities (CAs) you trust in the file root.crt in the data directory." I had ASS-U-MEd that root.crt would go in .postgresql as it does for encryption. This begs the question, why two copies of the same file?
Re: ssl client cert authentication
От:
Tom Lane <tgl@sss.pgh.pa.us>
Дата:
Ray Stell writes: > Someone asked about ssl client cert auth recently. I got > this to work, but something tripped me up. > http://developer.postgresql.org/pgdocs/postgres/ssl-tcp.html > states (very clearly, btw) that, "To require the client to supply a > trusted certificate, place certificates of the certificate authorities > (CAs) you trust in the file root.crt in the data directory." I had > ASS-U-MEd that root.crt would go in .postgresql as it does for encryption. > This begs the question, why two copies of the same file? The one in ~/.postgresql is for client usage. The one in $PGDATA is for the server's use. There's no reason to assume they'd be the same. regards, tom lane
Re: ssl client cert authentication
От:
Ray Stell <stellr@cns.vt.edu>
Дата:
On Mon, Nov 01, 2010 at 12:46:33PM -0400, Tom Lane wrote: > Ray Stell writes: > > Someone asked about ssl client cert auth recently. I got > > this to work, but something tripped me up. > > > http://developer.postgresql.org/pgdocs/postgres/ssl-tcp.html > > > states (very clearly, btw) that, "To require the client to supply a > > trusted certificate, place certificates of the certificate authorities > > (CAs) you trust in the file root.crt in the data directory." I had > > ASS-U-MEd that root.crt would go in .postgresql as it does for encryption. > > > This begs the question, why two copies of the same file? > > The one in ~/.postgresql is for client usage. The one in $PGDATA is for > the server's use. There's no reason to assume they'd be the same. > > regards, tom lane I think I see where I went off: 31.17. SSL Support Changing this to: 31.17. Client SSL Support would be helpful. Also, 31.17.4. SSL File Usage might be: 31.17.4. SSL Client File Usage They did this in the server section, so I'm not completely nuts: 17.8.2. SSL Server File Usage In hindsight it is very clear. Chapter 17 is on the server and 31 is on the client. Adding those section title words would have helped me stay on course. Another way of providing clue would be to add $PGDATA somewhere in Table 17-3. SSL Server File Usage. They did that sort of thing on the client side in Table 31-4. Libpq/Client SSL File Usage.
Re: ssl client cert authentication
От:
Bruce Momjian <bruce@momjian.us>
Дата:
Ray Stell wrote:
> On Mon, Nov 01, 2010 at 12:46:33PM -0400, Tom Lane wrote:
> > Ray Stell writes:
> > > Someone asked about ssl client cert auth recently. I got
> > > this to work, but something tripped me up.
> >
> > > http://developer.postgresql.org/pgdocs/postgres/ssl-tcp.html
> >
> > > states (very clearly, btw) that, "To require the client to supply a
> > > trusted certificate, place certificates of the certificate authorities
> > > (CAs) you trust in the file root.crt in the data directory." I had
> > > ASS-U-MEd that root.crt would go in .postgresql as it does for encryption.
> >
> > > This begs the question, why two copies of the same file?
> >
> > The one in ~/.postgresql is for client usage. The one in $PGDATA is for
> > the server's use. There's no reason to assume they'd be the same.
> >
> > regards, tom lane
>
> I think I see where I went off:
> 31.17. SSL Support
> Changing this to:
> 31.17. Client SSL Support
> would be helpful. Also,
> 31.17.4. SSL File Usage
> might be:
> 31.17.4. SSL Client File Usage
> They did this in the server section, so I'm not completely nuts:
> 17.8.2. SSL Server File Usage
>
> In hindsight it is very clear. Chapter 17 is on the server and 31 is on the
> client. Adding those section title words would have helped me stay on
> course.
>
> Another way of providing clue would be to add $PGDATA somewhere in Table
> 17-3. SSL Server File Usage. They did that sort of thing on the client side
> in Table 31-4. Libpq/Client SSL File Usage.
These are all very good ideas and I have applied them for 9.1 in the
attached patch. I also found a few libpq titles that needed
capitalization, which is also in the patch. Thanks for the ideas.
--
Bruce Momjian http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index fe661b8..1606a56 100644
*** /tmp/pgdiff.4616/aPwGCb_libpq.sgml Mon Jan 17 21:29:06 2011
--- doc/src/sgml/libpq.sgml Mon Jan 17 21:04:29 2011
*************** ldap://ldap.acme.com/cn=dbserver,cn=host
*** 6641,6647 ****
! Certificate verification
By default, PostgreSQL</> will not perform any verification of
--- 6641,6647 ----
! Client Verification of Server Certificates
By default, PostgreSQL</> will not perform any verification of
*************** ldap://ldap.acme.com/cn=dbserver,cn=host
*** 6696,6702 ****
! Client certificates
If the server requests a trusted client certificate,
--- 6696,6702 ----
! Client Certificates
If the server requests a trusted client certificate,
*************** ldap://ldap.acme.com/cn=dbserver,cn=host
*** 6738,6744 ****
! Protection provided in different modes
The different values for the sslmode</> parameter provide different
--- 6738,6744 ----
! Protection Provided in Different Modes
The different values for the sslmode</> parameter provide different
*************** ldap://ldap.acme.com/cn=dbserver,cn=host
*** 6746,6752 ****
protection against three types of attacks: