Project

General

Profile

Actions

Feature #2246

closed

[patch] ssl.use-sslv3

Added by ChiefBromden over 13 years ago. Updated over 10 years ago.

Status:
Fixed
Priority:
Normal
Category:
-
Target version:
ASK QUESTIONS IN Forums:

Description

Hi all,

I have recently "hardened" my SSL installation (fixing renegotiation, manually editing ciphersuites etc.) in an attempt to do at least as well as https://www.ssllabs.com/ssldb/analyze.html?d=cert.startcom.org

Long story short: It seems wise already now, but definitely for the future, to be able to turn off SSLv3 as well, and stick only with TLS, as SSLv3 also has weaknesses, and all current browsers support TLS 1.0 anyway.

I'm attaching a simple patch that allows to do precisely this. It's acting exactly like the ssl.use-sslv2 configuration, but for SSLv3 (and having the default as "enabled"). I verified this to work with the latest SVN revision of 1.4 (1.4.27-devel-2758M), but having looked at 1.5 source code it's straightforward to "port" it there as well.

If you think it's useful... well, just throw it in :-)


Files

sslv3-switch.patch (3.13 KB) sslv3-switch.patch ChiefBromden, 2010-08-11 19:58
Actions #1

Updated by ChiefBromden over 13 years ago

  • Target version set to 1.4.27
Actions #2

Updated by stbuehler over 13 years ago

  • Target version changed from 1.4.27 to 1.4.28
Actions #3

Updated by stbuehler over 13 years ago

  • Target version changed from 1.4.28 to 1.4.29
Actions #4

Updated by stbuehler about 13 years ago

  • Status changed from New to Fixed
  • % Done changed from 0 to 100

Applied in changeset r2780.

Actions #5

Updated by brad@comstyle.com about 13 years ago

With this patch applied and disabling SSLv3 I cannot get any
browser to connect. The error log shows messages such as the
following..

2011-03-16 22:36:24: (connections.c.299) SSL: 1 error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol
2011-03-16 22:36:49: (connections.c.299) SSL: 1 error:1408A10B:SSL routines:SSL3_GET_CLIENT_HELLO:wrong version number

Actions #6

Updated by stbuehler almost 13 years ago

One reason is that not all browsers support tls, the other is that tls does not work with openssl 1.0.0 right now, see #2269.

Actions #7

Updated by brad@comstyle.com almost 13 years ago

This works fine now that the fixes went in regarding ticket 2269.

Actions #8

Updated by iXce over 10 years ago

Hm, would it be possible to forward port this (and the other nice SSL patches, such as the one for use-compression) to trunk ?
Sorry if posting here is not the proper way to request this, but there's a nice "Missing in 1.5" field in the bug properties which is asking to be set to "Yes" :)

Actions #9

Updated by stbuehler over 10 years ago

1.5 isn't maintained anymore.

Actions

Also available in: Atom