Re: [Endymail] Improvements to S/MIME
Phillip Hallam-Baker <phill@hallambaker.com> Sat, 13 September 2014 18:46 UTC
Return-Path: <hallam@gmail.com>
X-Original-To: endymail@ietfa.amsl.com
Delivered-To: endymail@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 801A11A005E for <endymail@ietfa.amsl.com>; Sat, 13 Sep 2014 11:46:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 ridAFAXsq41b for <endymail@ietfa.amsl.com>; Sat, 13 Sep 2014 11:46:27 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 296531A007C for <endymail@ietf.org>; Sat, 13 Sep 2014 11:46:26 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id mc6so2639610lab.6 for <endymail@ietf.org>; Sat, 13 Sep 2014 11:46:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=U1UsClGRYLfKFXIHx8Rtpw8+Pz7Sm/ya+HuhwObPO3w=; b=g89LmfRYv83N+YUkQVGlW7lT9K7ZFz2c3Xh096y3WFHnQHiM+WU0sTt5WZcXmu56aw 7M/H16Pig7gxn31u+96TqJF92+lqqp0REjgBCIN0lY9S5YCNEoIBERKrqCqNeAMSonyH lza8KKm/jlcHkK4+AITAvN02m3+/g3p4u8ZeDZ8UQJcy0Dm0421Z/C9/XAO6Rhwfln9D zHUIEhrH6qR+LdQyJptfg3088/ZQyAe1BKGnoWf3TyV2OfAVq0bXcHlWFwaubb4GlM8M Wu+/6+z6uvWWRSuvnKf4y7JRIhXdWmzBT+MYrSGpx8ckryC5GG2rDVo3UjNUViXS+gRH SW+w==
MIME-Version: 1.0
X-Received: by 10.153.11.132 with SMTP id ei4mr17717875lad.24.1410633985501; Sat, 13 Sep 2014 11:46:25 -0700 (PDT)
Sender: hallam@gmail.com
Received: by 10.112.122.51 with HTTP; Sat, 13 Sep 2014 11:46:25 -0700 (PDT)
In-Reply-To: <87sijvmmo5.fsf@vigenere.g10code.de>
References: <CAAFsWK0VtnVvKwvkC1kjK+yKORkADVW1cKDx7nQ1fxA=dpZeTQ@mail.gmail.com> <87sijvmmo5.fsf@vigenere.g10code.de>
Date: Sat, 13 Sep 2014 14:46:25 -0400
X-Google-Sender-Auth: HluOiNbyb9kShY1a6UetxDwP9wc
Message-ID: <CAMm+LwivBifWKYMDBDocr4LCH40iVgP4zE2xXgEfkrb4bpN+Nw@mail.gmail.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
To: Werner Koch <wk@gnupg.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/endymail/aGEgTQP-RQqs9gl0iQTad1c84dw
Cc: Wei Chuang <weihaw@google.com>, endymail <endymail@ietf.org>
Subject: Re: [Endymail] Improvements to S/MIME
X-BeenThere: endymail@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <endymail.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/endymail>, <mailto:endymail-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/endymail/>
List-Post: <mailto:endymail@ietf.org>
List-Help: <mailto:endymail-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/endymail>, <mailto:endymail-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 13 Sep 2014 18:46:28 -0000
On Sat, Sep 13, 2014 at 1:54 PM, Werner Koch <wk@gnupg.org> wrote: > On Fri, 12 Sep 2014 19:48, weihaw@google.com said: > >> 1) S/MIME doesn't fully protect users mail envelope metadata. For example >> the recipient and envelope-sender must be visible to the intermediate SMTP > > If you want that, it is easy to put the messaqge into a message/rfc822 > mail container and use faked subject and other mailer header. Again there is a difference between what you can do and a standard. I think that 80% of what we need to do could be done in a profile of S/MIME that says stuff like * MUST support AES-128, AES-256 * MUST support [choose order of encrypt + sign] * MUST support domain level certs for end entity * MUST support message/rfc822 encrypted payload What we need to add on top is really not so difficult: * Mechanism for discovering recipient encryption preference, format support (PGP/SMIME), algorithm support and encryption key * Mechanism for direct trust, aka key fingerprint * Mechanism for private key maintenance But for any of it to work, we all have to do the same thing.
- [Endymail] Improvements to S/MIME Wei Chuang
- [Endymail] Improvements to S/MIME Arnt Gulbrandsen
- Re: [Endymail] Improvements to S/MIME Dave Crocker
- Re: [Endymail] Improvements to S/MIME Dave Crocker
- Re: [Endymail] Improvements to S/MIME Wei Chuang
- Re: [Endymail] Improvements to S/MIME Phillip Hallam-Baker
- Re: [Endymail] Improvements to S/MIME Werner Koch
- Re: [Endymail] Improvements to S/MIME Phillip Hallam-Baker
- Re: [Endymail] Improvements to S/MIME Wei Chuang
- Re: [Endymail] Improvements to S/MIME Wei Chuang
- Re: [Endymail] Improvements to S/MIME Werner Koch
- Re: [Endymail] Improvements to S/MIME Phillip Hallam-Baker
- Re: [Endymail] Improvements to S/MIME Cyrus Daboo
- Re: [Endymail] Improvements to S/MIME Phillip Hallam-Baker
- Re: [Endymail] Improvements to S/MIME Tom Mitchell
- Re: [Endymail] Improvements to S/MIME Phillip Hallam-Baker
- Re: [Endymail] Improvements to S/MIME Wei Chuang
- Re: [Endymail] Improvements to S/MIME Wei Chuang
- Re: [Endymail] Improvements to S/MIME Wei Chuang