This includes code comments and documentation. No backpatch as this is
cosmetic even if there are documentation changes which are user-facing.
Author: Daniel Gustafsson
Discussion: https://postgr.es/m/
BB89928E-2BC7-489E-A5E4-
6D204B3954CF@yesql.se
/* Blowfish */
/*
- * Check if strong crypto is supported. Some openssl installations
+ * Check if strong crypto is supported. Some OpenSSL installations
* support only short keys and unfortunately BF_set_key does not return any
* error value. This function tests if is possible to use strong key.
*/
Required for SSL support. Binaries can be downloaded from
+ or source from
s://www.openssl.org">.
To use a server-side third party library such as
python or
-
openssl, this library
must also be
+
OpenSSL, this library
must also be
64-bit. There is no support for loading a 32-bit library in a 64-bit
server. Several of the third party libraries that PostgreSQL supports may
only be available in 32-bit versions, in which case they cannot be used with
This is reportedly possible with some Windows versions of
This is reportedly possible with some Windows versions of
This is reportedly possible with some Windows versions of
- In MSVC builds, handle the case where the
openssl+ In MSVC builds, handle the case where the
OpenSSL library is not within a VC subdirectory (Andrew Dunstan)
- In MSVC builds, handle the case where the
openssl+ In MSVC builds, handle the case where the
OpenSSL library is not within a VC subdirectory (Andrew Dunstan)
- In MSVC builds, handle the case where the
openssl+ In MSVC builds, handle the case where the
OpenSSL library is not within a VC subdirectory (Andrew Dunstan)
- In MSVC builds, handle the case where the
openssl+ In MSVC builds, handle the case where the
OpenSSL library is not within a VC subdirectory (Andrew Dunstan)
Branch: REL9_2_STABLE [f964a7c5a] 2017-06-05 20:41:01 -0400
-->
- In MSVC builds, handle the case where the
openssl+ In MSVC builds, handle the case where the
OpenSSL library is not within a VC subdirectory (Andrew Dunstan)
SSL_CTX_set_options(context, SSL_OP_NO_SSLv2 | SSL_OP_NO_SSLv3);
/* disallow SSL session tickets */
-#ifdef SSL_OP_NO_TICKET /* added in openssl 0.9.8f */
+#ifdef SSL_OP_NO_TICKET /* added in OpenSSL 0.9.8f */
SSL_CTX_set_options(context, SSL_OP_NO_TICKET);
#endif
* Private substitute BIO: this does the sending and receiving using send() and
* recv() instead. This is so that we can enable and disable interrupts
* just while calling recv(). We cannot have interrupts occurring while
- * the bulk of openssl runs, because it uses malloc() and possibly other
+ * the bulk of OpenSSL runs, because it uses malloc() and possibly other
* non-reentrant libc facilities. We also need to call send() and recv()
* directly so it gets passed through the socket/signals layer on Win32.
*
return my_bio_methods;
}
-/* This should exactly match openssl's SSL_set_fd except for using my BIO */
+/* This should exactly match OpenSSL's SSL_set_fd except for using my BIO */
static int
my_SSL_set_fd(Port *port, int fd)
{
return my_bio_methods;
}
-/* This should exactly match openssl's SSL_set_fd except for using my BIO */
+/* This should exactly match OpenSSL's SSL_set_fd except for using my BIO */
static int
my_SSL_set_fd(PGconn *conn, int fd)
{
# This target generates all the key and certificate files.
sslfiles: $(SSLFILES)
-# Openssl requires a directory to put all generated certificates in. We don't
+# OpenSSL requires a directory to put all generated certificates in. We don't
# use this for anything, but we need a location.
ssl/new_certs_dir:
mkdir ssl/new_certs_dir
projects / postgresql.git / commitdiff