Date: Thu, 13 Oct 2005 13:44:28 -0700 From: Jacques Vidrine <jacques@vidrine.us> To: Peter Jeremy <PeterJeremy@optushome.com.au> Cc: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-05:21.openssl Message-ID: <47D785F8-E28E-4753-ABE9-8627107D9038@vidrine.us> In-Reply-To: <20051012191019.GJ2482@cirb503493.alcatel.com.au> References: <200510111202.j9BC2obf081876@freefall.freebsd.org> <434BCB75.2000402@iang.org> <B9EA75B5-B5AE-4164-A91E-061E5AECCC5B@vidrine.us> <20051012191019.GJ2482@cirb503493.alcatel.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-10-12, at 12:10 :19, Peter Jeremy wrote: > On Tue, 2005-Oct-11 09:45:53 -0700, Jacques Vidrine wrote: >> On Oct 11, 2005, at 7:25 AM, Ian G wrote: >>> Isn't the workaround obviously to switch off V2? >> >> Yes. Sorry that wasn't mentioned. > > That sounds like a good workaround. How do I implement it? I've > looked through the documentation and can't find any reference to a > runtime OpenSSL configuration file that would let me do this. I'm not aware of a global option for OpenSSL, either. Disabling SSLv2 would need to be handled by the application, i.e. turn off SSLv2 for each of your SSL/TLS applications. Cheers, -- Jacques Vidrine <jacques@vidrine.us>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47D785F8-E28E-4753-ABE9-8627107D9038>