Re: BUG #13578: use cipher=NULL-SHA256 error when connect

From: 德哥 <digoal(at)126(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #13578: use cipher=NULL-SHA256 error when connect
Date: 2015-08-19 03:11:17
Message-ID: 66111007.57e2.14f43f07b51.Coremail.digoal@126.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

At 2015-08-19 05:32:40, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>digoal(at)126(dot)com writes:
>> why PostgreSQL 9.4.4 cann't use eNULL or NULL ciphers?
>
>I believe we intentionally disallow that, because those "ciphers"
>actually mean transmission in cleartext. If you're okay with
>unencrypted connections, you needn't bother with SSL at all.
>

> regards, tom lane

yes, but when people hope to use SSL's compression function, and don't need encrypted these data?
the encryption will use some CPU, so it's performance will reduce little.

regards, digoal

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message ppmichalakk 2015-08-19 14:48:51 BUG #13579: Server crashes after executing plpythonu function
Previous Message Tom Lane 2015-08-18 21:32:40 Re: BUG #13578: use cipher=NULL-SHA256 error when connect