On Tue, Feb 20, 2007 at 05:08:07PM +0100, Bodo Moeller wrote:
> On Mon, Feb 19, 2007 at 03:22:44PM -0500, Victor Duchovni wrote:
>
> > As far as the 0.9.9 patch is concerned, is it possible to cache the
> > initial sorted order? Some applications process cipherlists for every
> > connection (destination dependent cipher lists), and it would be nice to
> > keep this efficient, provided that there is negligbible or no additional
> > cost for applications that set the cipherlist only once.
>
> It's true that the sorted order of "ALL" should be generated just
> once, and then cached, for better efficiency. Where and how to do
> this caching, though, is an optimization decision that will introduce
> certain complications, and should only be done once we are sure that
> the ciphersuite sorting code itself is OK.
Makes sense.
> I'm thinking of caching the sorted list once per SSL_CTX, eventually.
That seems very reasonable. In the mean-time, in Postfix 2.4, I am
caching the cipher_list string that was last applied to SSL_CTX, so in
the typical case that successive connections re-use the same cipherlist,
additional NOOP calls to SSL_CTX_set_cipher_list() are avoided.
--
Viktor.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List [email protected]
Automated List Manager [EMAIL PROTECTED]