postgresql

History

Tom Lane fd9e2accef When we are in error recursion trouble, arrange to suppress translation and encoding conversion of any elog/ereport message being sent to the frontend. This generalizes a patch that I put in last October, which suppressed translation of only specific messages known to be associated with recursive can't-translate-the-message behavior. As shown in bug #4680, we need a more general answer in order to have some hope of coping with broken encoding conversion setups. This approach seems a good deal less klugy anyway. Patch in all supported branches.		2009-03-02 21:18:43 +00:00
..
Makefile	Refactor backend makefiles to remove lots of duplicate code	2008-02-19 10:30:09 +00:00
README.SSL	Remove large parts of the old SSL readme, that consisted of a couple	2008-10-24 11:48:29 +00:00
auth.c	Make krb_realm and krb_server_hostname be pg_hba options only, and remove	2009-01-09 10:13:19 +00:00
be-fsstubs.c	Update copyright for 2009.	2009-01-01 17:24:05 +00:00
be-secure.c	Go over all OpenSSL return values and make sure we compare them	2009-01-28 15:06:47 +00:00
crypt.c	Update copyright for 2009.	2009-01-01 17:24:05 +00:00
hba.c	Add hba parameter include_realm to krb5, gss and sspi authentication, used	2009-01-07 13:09:21 +00:00
ip.c	Tweak the existing special case for AIX in pg_getaddrinfo_all() to handle	2009-01-23 19:58:06 +00:00
md5.c	Update copyright for 2009.	2009-01-01 17:24:05 +00:00
pg_hba.conf.sample	Add support for using SSL client certificates to authenticate to the	2008-11-20 11:48:26 +00:00
pg_ident.conf.sample	Support regular expressions in pg_ident.conf.	2008-11-28 14:26:58 +00:00
pqcomm.c	Update copyright for 2009.	2009-01-01 17:24:05 +00:00
pqformat.c	When we are in error recursion trouble, arrange to suppress translation and	2009-03-02 21:18:43 +00:00
pqsignal.c	Update copyright for 2009.	2009-01-01 17:24:05 +00:00

README.SSL

$PostgreSQL: pgsql/src/backend/libpq/README.SSL,v 1.7 2008/10/24 11:48:29 mha Exp $

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

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