Re: IETF mail server and SSLv3

Viktor Dukhovni <ietf-dane@dukhovni.org> Fri, 26 February 2016 23:47 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B49181B33C3 for <ietf@ietfa.amsl.com>; Fri, 26 Feb 2016 15:47:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XDYcjiX_KJAu for <ietf@ietfa.amsl.com>; Fri, 26 Feb 2016 15:47:47 -0800 (PST)
Received: from mournblade.imrryr.org (mournblade.imrryr.org [38.117.134.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8FB11B33C2 for <ietf@ietf.org>; Fri, 26 Feb 2016 15:47:47 -0800 (PST)
Received: from [10.24.16.2] (mobile-166-171-186-052.mycingular.net [166.171.186.52]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mournblade.imrryr.org (Postfix) with ESMTPSA id AED8F282F4E for <ietf@ietf.org>; Fri, 26 Feb 2016 23:47:45 +0000 (UTC) (envelope-from ietf-dane@dukhovni.org)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
Subject: Re: IETF mail server and SSLv3
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <56D0D9A2.9040100@ultrawaves.fr>
Date: Fri, 26 Feb 2016 18:46:46 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <98DDE526-410D-4E40-83E1-083F47715E5A@dukhovni.org>
References: <20160225080725.822301A43E@ld9781.wdf.sap.corp> <B608EA62-EF66-4739-A0BF-42BA9B5FB307@dukhovni.org> <56D0D9A2.9040100@ultrawaves.fr>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/KfXTa4SmOSehZm3gCB9oV_Mi8fg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Feb 2016 23:47:49 -0000

> On Feb 26, 2016, at 6:02 PM, Solarus <solarus@ultrawaves.fr> wrote:
> 
>>> Disabling SSLv3 can not possibly provide any security benefit here,
>>> but may cause interop problems and less security for a few old peers.
>> 
>> Would you then go further and say that SMTP servers should leave SSLv2
>> and/or EXPORT ciphers or single-DES enabled?  If not, why not?
> 
> No.

"No" as in they should not leave SSLv2/EXPORT/1DES enabled?

> But with SMTP, STARTTLS is an opportunistic encryption, if you don't
> support the maximum of ciphers, the other server will send you mails in
> cleartext.
> And it's worse to receive and send mail in cleartext than with a weak
> encryption.

Your rationale seems to contradict the "No" response.

-- 
	Viktor.