Re: [lamps] S/MIME fix

Russ Housley <housley@vigilsec.com> Thu, 17 May 2018 13:42 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8DE12EB15 for <spasm@ietfa.amsl.com>; Thu, 17 May 2018 06:42:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level:
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 pOP0u975RbSS for <spasm@ietfa.amsl.com>; Thu, 17 May 2018 06:42:47 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1D21112EB37 for <SPASM@ietf.org>; Thu, 17 May 2018 06:42:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 0A012300A2D for <SPASM@ietf.org>; Thu, 17 May 2018 09:42:45 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id tzV8pSxypRDa for <SPASM@ietf.org>; Thu, 17 May 2018 09:42:40 -0400 (EDT)
Received: from new-host.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 02E783005C5 for <SPASM@ietf.org>; Thu, 17 May 2018 09:42:39 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_46B555DA-F817-4324-A520-73BBE703970E"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Thu, 17 May 2018 09:42:43 -0400
References: <CAMm+Lwj=VTBHYxH-iOaqEUHxALpBfSXWG3p0+xxUnY+o4CmGvA@mail.gmail.com> <559ab3c7-ee5f-22b9-ef02-c091765011d2@isode.com> <04ca01d3ed3c$5c158050$144080f0$@augustcellars.com> <951633c7-0cad-58e7-236c-bb82e44c9e9f@isode.com>
To: SPASM <SPASM@ietf.org>
In-Reply-To: <951633c7-0cad-58e7-236c-bb82e44c9e9f@isode.com>
Message-Id: <C7E25B09-D462-4620-97E1-F44F16BD20B7@vigilsec.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/_hKEFEObp4m-UM4WWzvxG9E6LCk>
Subject: Re: [lamps] S/MIME fix
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2018 13:42:57 -0000

On May 16, 2018, at 1:51 PM, Alexey Melnikov <alexey.melnikov@isode.com> wrote:
> On 16/05/2018 18:35, Jim Schaad wrote:
> 
>> I will note that unless multipart/mixed has some special text associated with it.  Text/html is defined by RFC 1866 to only hold a single HTML document.  Thus building an HTML document from multiple parts is not according to Hoyle.
> Yes, but people do this anyway, as separate HTML body parts are frequently valid HTML documents. So building from pieces works most(*) of the time.
> 
> (*) spam and phishing nonwithstanding.

I do not see a way to totally thwart eFail unless each portion of a multi-part is processed in its own sandbox.

Russ