mirror of
https://github.com/postgres/postgres.git
synced 2025-09-02 04:21:28 +03:00
Move EDH support to common files
The EDH support is not really specific to the OpenSSL implementation, so move the support and documentation comments to common files.
This commit is contained in:
@@ -58,3 +58,25 @@ SSL
|
||||
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()).
|
||||
|
Reference in New Issue
Block a user