![]() For these reasons NULL ciphers are not recommended. Also, encryption overhead is minimal compared to the overhead of authentication. However, a man-in-the-middle could read and pass communications between client and server. It is possible to have authentication without encryption overhead by using NULL-SHA or NULL-MD5 ciphers. While a list of ciphers can be specified in the OpenSSL configuration file, you can specify ciphers specifically for use by the database server by modifying ssl_ciphers in nf. OpenSSL supports a wide range of ciphers and authentication algorithms, of varying strength. This default can be overridden by setting environment variable OPENSSL_CONF to the name of the desired configuration file. By default, this file is named openssl.cnf and is located in the directory reported by openssl version -d. PostgreSQL reads the system-wide OpenSSL configuration file. By default, this is at the client's option see Section 20.1 about how to set up the server to require use of SSL for some or all connections. ![]() The server will listen for both normal and SSL connections on the same TCP port, and will negotiate with any connecting client on whether to use SSL. With SSL support compiled in, the PostgreSQL server can be started with SSL enabled by setting the parameter ssl to on in nf. This requires that OpenSSL is installed on both client and server systems and that support in PostgreSQL is enabled at build time (see Chapter 16). PostgreSQL has native support for using SSL connections to encrypt client/server communications for increased security. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |