Skip to content
Snippets Groups Projects
Select Git revision
  • benchmark-tools
  • postgres-lambda
  • master default
  • REL9_4_25
  • REL9_5_20
  • REL9_6_16
  • REL_10_11
  • REL_11_6
  • REL_12_1
  • REL_12_0
  • REL_12_RC1
  • REL_12_BETA4
  • REL9_4_24
  • REL9_5_19
  • REL9_6_15
  • REL_10_10
  • REL_11_5
  • REL_12_BETA3
  • REL9_4_23
  • REL9_5_18
  • REL9_6_14
  • REL_10_9
  • REL_11_4
23 results

configure

Blame
    • Bruce Momjian's avatar
      902ca3e2
      Here is a patch to fix win32 ssl builds. Summary of changes: · 902ca3e2
      Bruce Momjian authored
      * Links with -leay32 and -lssleay32 instead of crypto and ssl. On win32,
      "crypto and ssl" is only used for static linking.
      
      * Initializes SSL in the backend and not just in the postmaster. We
      cannot pass the SSL context from the postmaster through the parameter
      file, because it contains function pointers.
      
      * Split one error check in be-secure.c. Previously we could not tell
      which of three calls actually failed. The previous code also returned
      incorrect error messages if SSL_accept() failed - that function needs to
      use SSL_get_error() on the return value, can't just use the error queue.
      
      * Since the win32 implementation uses non-blocking sockets "behind the
      scenes" in order to deliver signals correctly, implements a version of
      SSL_accept() that can handle this. Also, add a wait function in case
      SSL_read or SSL_write() needs more data.
      
      Magnus Hagander
      902ca3e2
      History
      Here is a patch to fix win32 ssl builds. Summary of changes:
      Bruce Momjian authored
      * Links with -leay32 and -lssleay32 instead of crypto and ssl. On win32,
      "crypto and ssl" is only used for static linking.
      
      * Initializes SSL in the backend and not just in the postmaster. We
      cannot pass the SSL context from the postmaster through the parameter
      file, because it contains function pointers.
      
      * Split one error check in be-secure.c. Previously we could not tell
      which of three calls actually failed. The previous code also returned
      incorrect error messages if SSL_accept() failed - that function needs to
      use SSL_get_error() on the return value, can't just use the error queue.
      
      * Since the win32 implementation uses non-blocking sockets "behind the
      scenes" in order to deliver signals correctly, implements a version of
      SSL_accept() that can handle this. Also, add a wait function in case
      SSL_read or SSL_write() needs more data.
      
      Magnus Hagander
    configure 531.59 KiB