From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sean Chittenden <sean@chittenden.org>
Cc: pgsql-hackers@postgreSQL.org
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: Speed of SSL connections; cost of renegotiation
Date: Thu, 10 Apr 2003 23:05:53 -0400
Message-ID: <8640.1050030353@sss.pgh.pa.us> (raw)
In-Reply-To: <20030411025825.GK79923@perrin.int.nxad.com>
References: <7334.1050015002@sss.pgh.pa.us>
<20030411011557.GJ79923@perrin.int.nxad.com>
<8486.1050028983@sss.pgh.pa.us>
<20030411025825.GK79923@perrin.int.nxad.com>
Sean Chittenden <sean@chittenden.org> writes:
>> From sshd(8):
> -k key_gen_time
> Specifies how often the ephemeral protocol version 1 server key
> is regenerated (default 3600 seconds, or one hour).
Hmmm. But a server key isn't the same as a session key, is it? Is this
an argument for renegotiating session keys at all?
In any case, you can pump a heck of a lot of data through ssh in an
hour. Based on that, it sure looks to me like every-64K is a
ridiculously small setting. If we were to crank it up to a few meg, the
performance issue would go away, and we'd not really need to think about
changing to a time-based criterion.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, sean@chittenden.org, pgsql-hackers@postgreSQL.org
Subject: Re: Speed of SSL connections; cost of renegotiation
In-Reply-To: <8640.1050030353@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox