Re: What happened to SSL_CIPHERS? - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: What happened to SSL_CIPHERS?
Date
Msg-id AANLkTi=eL4SbrjkivT8a22bPQ5gmOeAkV6qY9DjoQYnM@mail.gmail.com
Whole thread Raw
In response to What happened to SSL_CIPHERS?  (Josh Berkus <josh@agliodbs.com>)
Responses Re: What happened to SSL_CIPHERS?  (Josh Berkus <josh@agliodbs.com>)
List pgsql-bugs
On Thu, Oct 28, 2010 at 22:33, Josh Berkus <josh@agliodbs.com> wrote:
> Folks,
>
> This doc says we ought to have the ssl_ciphers parameter:
>
> http://www.postgresql.org/docs/9.0/static/runtime-config-connection.html#=
RUNTIME-CONFIG-CONNECTION-SECURITY
>
> Nor is there anything in the 9.0 release notes about it going away.
>
> Yet:
>
> postgres=3D# select version();
> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 =A0 =A0 =A0 =A0 =A0 version
> -------------------------------------------------------------------------=
--------------------------------
> =A0PostgreSQL 9.0.1 on x86_64-unknown-linux-gnu, compiled by GCC gcc (Ubu=
ntu
> 4.3.3-5ubuntu4) 4.3.3, 64-bit
> (1 row)
>
> postgres=3D# show ssl_ciphers;
> ERROR: =A0unrecognized configuration parameter "ssl_ciphers"
>
> So, did ssl_ciphers go away on purpose? =A0If so, why? =A0If not, why isn=
't it
> accessible?

Are you sure you're on an SSL enabled build?

--=20
=A0Magnus Hagander
=A0Me: http://www.hagander.net/
=A0Work: http://www.redpill-linpro.com/

pgsql-bugs by date:

Previous
From: Josh Berkus
Date:
Subject: What happened to SSL_CIPHERS?
Next
From: Robert Haas
Date:
Subject: Re: BUG #5707: Cross compilation for windows is broken