Skip site navigation (1) Skip section navigation (2)

Re: Backend SSL configuration enhancement

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 (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2006-08-30 14:52:50
Subject: Re: [PATCHES] Backend SSL configuration enhancement
Previous:From: Michael GlaesemannDate: 2006-08-30 13:20:58
Subject: Re: [HACKERS] Interval aggregate regression failure (expected seems

pgsql-patches by date

Next:From: Andrew DunstanDate: 2006-08-30 14:52:50
Subject: Re: [PATCHES] Backend SSL configuration enhancement
Previous:From: Michael GlaesemannDate: 2006-08-30 13:20:58
Subject: Re: [HACKERS] Interval aggregate regression failure (expected seems

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group