From: Tom Lane <tgl@sss.pgh.pa.us>
To: Curt Sampson <cjs@cynic.net>
Cc: scott.marlowe <scott.marlowe@ihs.com>
Cc: pgsql-hackers@postgresql.org
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Speed of SSL connections; cost of renegotiation
Date: Sat, 12 Apr 2003 01:26:26 -0400
Message-ID: <16304.1050125186@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.NEB.4.51.0304121258300.624@angelic-vtfw.cvpn.cynic.net>
References: <Pine.LNX.4.33.0304110855430.2900-100000@css120.ihs.com>
<11759.1050074673@sss.pgh.pa.us>
<Pine.NEB.4.51.0304121258300.624@angelic-vtfw.cvpn.cynic.net>
Curt Sampson <cjs@cynic.net> writes:
> On Fri, 11 Apr 2003, Tom Lane wrote:
>> I realized this morning that there's probably a security tradeoff
>> involved: renegotiating the session key limits the amount of session
>> data encrypted with any one key, which is good; but each renegotiation
>> requires another use of the server key, increasing the odds that an
>> eavesdropper could break *that* (which'd let him into all sessions not
>> just the one).
> This seems extremely low-risk to me; there's very little data
> transferred using the server key.
Perhaps, but the downside if the server key is broken is much worse
than the loss if any one session key is broken. Also, I don't know
how stylized the key-renegotiation exchange is --- there might be
a substantial known-plaintext risk there.
The fact that sshd thinks it necessary to choose a new server key as
often as once an hour indicates to me that they consider the risks
nonnegligible.
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, cjs@cynic.net, scott.marlowe@ihs.com, pgsql-hackers@postgresql.org
Subject: Re: Speed of SSL connections; cost of renegotiation
In-Reply-To: <16304.1050125186@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