From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org, "Victor B(dot) Wagner" <vitus(at)cryptocom(dot)ru> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: Backend SSL configuration enhancement |
Date: | 2006-08-30 14:14:02 |
Message-ID: | 26942.1156947242@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
"Victor B. Wagner" <vitus(at)cryptocom(dot)ru> writes:
> This patch adds two new configuration diretives to postgresql.conf file
> 1. ssl_ciphers - allows server administrator to specify set of SSL
> ciphersuites which can be used by clients to connect the server.
> 2. ssl_engine - allows to specify loadable crypto engin (i.e. hardware
> crypto accelerator support) to use.
Why are either of these useful? What are the compatibility implications
of changing them? Does the addition of the engine-load code break
compatibility with older OpenSSL releases?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-08-30 14:52:50 | Re: [PATCHES] Backend SSL configuration enhancement |
Previous Message | Michael Glaesemann | 2006-08-30 13:20:58 | Re: [HACKERS] Interval aggregate regression failure (expected seems |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-08-30 14:52:50 | Re: [PATCHES] Backend SSL configuration enhancement |
Previous Message | Michael Glaesemann | 2006-08-30 13:20:58 | Re: [HACKERS] Interval aggregate regression failure (expected seems |