postgresql

History

Peter Eisentraut f60a0e9677 Add more columns to pg_stat_ssl Add columns client_serial and issuer_dn to pg_stat_ssl. These allow uniquely identifying the client certificate. Rename the existing column clientdn to client_dn, to make the naming more consistent and easier to read. Discussion: https://www.postgresql.org/message-id/flat/398754d8-6bb5-c5cf-e7b8-22e5f0983caf@2ndquadrant.com/		2019-02-01 00:33:47 +01:00
..
Makefile	Add ssl_passphrase_command setting	2018-03-17 08:28:51 -04:00
README.SSL	Move EDH support to common files	2018-01-23 07:11:38 -05:00
auth-scram.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
auth.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
be-fsstubs.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
be-secure-common.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
be-secure-openssl.c	Add more columns to pg_stat_ssl	2019-02-01 00:33:47 +01:00
be-secure.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
crypt.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
hba.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
ifaddr.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
pg_hba.conf.sample	Rename "scram" to "scram-sha-256" in pg_hba.conf and password_encryption.	2017-04-18 14:50:50 +03:00
pg_ident.conf.sample	Reformat the comments in pg_hba.conf and pg_ident.conf	2010-01-26 06:58:39 +00:00
pqcomm.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
pqformat.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
pqmq.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00
pqsignal.c	Update copyright for 2019	2019-01-02 12:44:25 -05:00

README.SSL

src/backend/libpq/README.SSL

SSL
===

>From the servers perspective:


  Receives StartupPacket
           |
           |
 (Is SSL_NEGOTIATE_CODE?) -----------  Normal startup
           |                  No
           |
           | Yes
           |
           |
 (Server compiled with USE_SSL?) ------- Send 'N'
           |                       No        |
           |                                 |
           | Yes                         Normal startup
           |
           |
        Send 'S'
           |
           |
      Establish SSL
           |
           |
      Normal startup





>From the clients perspective (v6.6 client _with_ SSL):


      Connect
         |
         |
  Send packet with SSL_NEGOTIATE_CODE
         |
         |
  Receive single char  ------- 'S' -------- Establish SSL
         |                                       |
         | '<else>'                              |
         |                                  Normal startup
         |
         |
   Is it 'E' for error  ------------------- Retry connection
         |                  Yes             without SSL
         | No
         |
   Is it 'N' for normal ------------------- Normal startup
         |                  Yes
         |
   Fail with unknown

---------------------------------------------------------------------------

Ephemeral DH
============

Since the server static private key ($DataDir/server.key) will
normally be stored unencrypted so that the database backend can
restart automatically, it is important that we select an algorithm
that continues to provide confidentiality even if the attacker has the
server's private key.  Ephemeral DH (EDH) keys provide this and more
(Perfect Forward Secrecy aka PFS).

N.B., the static private key should still be protected to the largest
extent possible, to minimize the risk of impersonations.

Another benefit of EDH is that it allows the backend and clients to
use DSA keys.  DSA keys can only provide digital signatures, not
encryption, and are often acceptable in jurisdictions where RSA keys
are unacceptable.

The downside to EDH is that it makes it impossible to use ssldump(1)
if there's a problem establishing an SSL session.  In this case you'll
need to temporarily disable EDH (see initialize_dh()).