postgresql

History

Tom Lane 792b0f4666 Get rid of not-very-portable fcntl(F_SETLK) mechanism for locking the Unix socket file, in favor of having an ordinary lockfile beside the socket file. Clean up a few robustness problems in the lockfile code. If postmaster is going to reject a connection request based on database state, it will now tell you so before authentication exchange not after. (Of course, a failure after is still possible if conditions change meanwhile, but this makes life easier for a yet-to-be-written pg_ping utility.)		2000-11-29 20:59:54 +00:00
..
Makefile	Make the location of the Kerberos server key file run time configurable	2000-08-25 10:00:35 +00:00
README.SSL	Add README.SSL	1999-09-27 03:16:09 +00:00
auth.c	Make the location of the Kerberos server key file run time configurable	2000-08-25 10:00:35 +00:00
be-fsstubs.c	Remove arbitrary limit on number of simultaneously open large objects.	2000-10-24 03:14:08 +00:00
crypt.c	Clean up callers of AllocateFile and BasicOpenFile to ensure that	2000-08-27 21:50:18 +00:00
hba.c	Clean up callers of AllocateFile and BasicOpenFile to ensure that	2000-08-27 21:50:18 +00:00
password.c	Be a little more careful with strtok().	2000-11-27 03:46:01 +00:00
pg_hba.conf.sample	Improve comments in pg_hba.conf.sample and the associated SGML	2000-11-21 20:44:32 +00:00
pg_ident.conf.sample	Improve comments.	2000-11-21 20:48:38 +00:00
pqcomm.c	Get rid of not-very-portable fcntl(F_SETLK) mechanism for locking the Unix	2000-11-29 20:59:54 +00:00
pqformat.c	Remove a bunch of unused configure tests, in particular cases where	2000-07-12 22:59:15 +00:00
pqpacket.c	New diff that now covers the entire tree. Applying this gets postgresql	2000-10-03 03:11:26 +00:00
pqsignal.c	Add SIGFPE to list of signals never to block. #ifdef all signals in	2000-06-29 02:17:42 +00:00
util.c	Remove long-dead support for invoking queries from dynamically loaded	2000-07-08 03:04:41 +00:00

README.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