From 0d5b4f594dfb03828b7be26b083c8afae2409896 Mon Sep 17 00:00:00 2001 From: Richard Levitte Date: Thu, 12 Jun 2003 01:04:12 +0000 Subject: [PATCH] Typo. PR: 584 --- bugs/SSLv3 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/bugs/SSLv3 b/bugs/SSLv3 index db53e1343a..a75a1652d9 100644 --- a/bugs/SSLv3 +++ b/bugs/SSLv3 @@ -29,7 +29,7 @@ RC4-MD5, but a re-connect tries to use DES-CBC-SHA. So netscape, when doing a re-connect, always takes the first cipher in the cipher list. If we accept a netscape connection, demand a client cert, have a -non-self-sighed CA which does not have it's CA in netscape, and the +non-self-signed CA which does not have it's CA in netscape, and the browser has a cert, it will crash/hang. Works for 3.x and 4.xbeta Netscape browsers do not really notice the server sending a