From owner-freebsd-gecko@FreeBSD.ORG  Fri Oct 17 04:35:21 2014
Return-Path: <owner-freebsd-gecko@FreeBSD.ORG>
Delivered-To: gecko@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A26EB4BD;
 Fri, 17 Oct 2014 04:35:21 +0000 (UTC)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com
 [IPv6:2607:f8b0:4001:c03::22e])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 61046EDF;
 Fri, 17 Oct 2014 04:35:21 +0000 (UTC)
Received: by mail-ie0-f174.google.com with SMTP id tr6so42157ieb.19
 for <multiple recipients>; Thu, 16 Oct 2014 21:35:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :cc:content-type:content-transfer-encoding;
 bh=ewapvnMs6kO2B+Wod0ZQ1odMyyi3T9txzWTE8q8ketM=;
 b=Ddm9/uFmhD5DCxreA9sclOEibeXbwIyebJgsk9yz8+3U/KIeBzWWEFwDO2EFcZJgHk
 CbfzdAOchPvfIrIXXln0ca9iAa8SgpteYYCV4ga52Im6uX9JRwdw6xHMGY5p/ilnt1OZ
 hdbnyteR2SdLsJWQFiP28tjAxtl5m3olLmrhLIz3qnXvtQ56QcT+9dj+tS/Om2YvBFFI
 qSKt3YFv8hh8rMcsQECNdOnK4NCwZ2lfLldDOIMNVn+TuLek+ZL0qpABq0hmjzsSByqm
 fqWLlQzLzGjcgDM5vMe5CvT57SKrZ9Z49HYMKxPT1iMZXKtDdHtpjyCjA4rv1FgLWlQk
 abxw==
X-Received: by 10.42.62.129 with SMTP id y1mr7915125ich.19.1413520520719; Thu,
 16 Oct 2014 21:35:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.175.28 with HTTP; Thu, 16 Oct 2014 21:34:50 -0700 (PDT)
In-Reply-To: <86iojmgn40.fsf@nine.des.no>
References: <86iojmgn40.fsf@nine.des.no>
From: Jia-Shiun Li <jiashiun@gmail.com>
Date: Fri, 17 Oct 2014 12:34:50 +0800
Message-ID: <CAHNYxxP1h8P=fGcVGAXeOAU=DCweNYYa2vcypsB8KGkjBR1MOQ@mail.gmail.com>
Subject: Re: POODLE SSLv3 vulnerability
To: =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= <des@des.no>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: gecko@freebsd.org, ports-secteam@freebsd.org, chromium@freebsd.org
X-BeenThere: freebsd-gecko@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Gecko Rendering Engine issues <freebsd-gecko.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-gecko>,
 <mailto:freebsd-gecko-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-gecko/>
List-Post: <mailto:freebsd-gecko@freebsd.org>
List-Help: <mailto:freebsd-gecko-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gecko>,
 <mailto:freebsd-gecko-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Oct 2014 04:35:21 -0000

On Wed, Oct 15, 2014 at 9:03 AM, Dag-Erling Sm=C3=B8rgrav <des@des.no> wrot=
e:
> I would also like to do the same for Chrome, but I don't know the exact
> procedure and I am unable to find out or test, since Chrome has been
> broken for several months.

according to askubuntu[1], for Chromium it is as simple as adding
--ssl-version-min=3Dtls1 in command line. It can be added to the
/usr/local/bin/chrome script executing the actual binary.


[1]: http://askubuntu.com/questions/537196/how-do-i-patch-workaround-sslv3-=
poodle-vulnerability-cve-2014-3566


-Jia-Shiun.