IETF Logo Mail Archive

Re: [ietf-smtp] How to encrypt SMTP?

"John Levine" <johnl@taugh.com> Sat, 26 October 2019 19:00 UTC

Return-Path: <johnl@iecc.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADBE0120088 for <ietf-smtp@ietfa.amsl.com>; Sat, 26 Oct 2019 12:00:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=oiZ+l1QG; dkim=pass (1536-bit key) header.d=taugh.com header.b=hxcGMx94
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 rqgTrI8WQeOL for <ietf-smtp@ietfa.amsl.com>; Sat, 26 Oct 2019 12:00:01 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D58D120048 for <ietf-smtp@ietf.org>; Sat, 26 Oct 2019 12:00:01 -0700 (PDT)
Received: (qmail 52272 invoked from network); 26 Oct 2019 18:59:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=cc2e.5db497af.k1910; i=printer-iecc.com@submit.iecc.com; bh=zcTmm4Re8NvJJqfatGFJvZwjGkv52w0TnaKmWpi9dZw=; b=oiZ+l1QGL2s5woQ0uE2CnhRQ4ZVlzuhc22cQI/HjTb9nc4tBO1SZUSa5RrJ2vW8kceDlvw7kcar7vmP9SCnvENqmUp6mvMN/wb7/mml1oBYiEEwY/qTEN62pFXKcVaxqOqszer1q/QRPEz/ZElVZu3cyDPQV4OGoJdbkaah8JYoGN2etId7sJMg46TmFcCFb2ft9ldLX8Tq39Yt8YF5ZVKp2zu207YShrRXNGhZ5AkDI1TCNk3c82eVjsHefrm+j
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=cc2e.5db497af.k1910; olt=printer-iecc.com@submit.iecc.com; bh=zcTmm4Re8NvJJqfatGFJvZwjGkv52w0TnaKmWpi9dZw=; b=hxcGMx94sKqqZQbmjwK1bZ1FbKkucWm9VNOX+oTr+0jsJP62inVbQgX2kBUhfU+rNiVsA0GL0zg2GFI+zRfW6HEc+YmpuhTz2d4/s6dfMcNe/J9ZWc9NJ6qXVMXJEKo/IxxXBAXqAq+0a2U7w3ZNt4ldqCV885ODzh6w9S8Dqte9t/8gC0AJp5PaVlzRy1BkO1+Bj6d+VcMEeiOPp1nrZjdl19HbjYg3lN9W+CLVJAGpkpI4F69bPXq+DZ6QoGwT
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPSA (TLS1.2 ECDHE-RSA AES-256-GCM AEAD, printer@iecc.com) via TCP6; 26 Oct 2019 18:59:59 -0000
Received: by ary.qy (Postfix, from userid 501) id C9490D7128E; Sat, 26 Oct 2019 14:59:58 -0400 (EDT)
Date: Sat, 26 Oct 2019 14:59:58 -0400
Message-Id: <20191026185958.C9490D7128E@ary.qy>
From: John Levine <johnl@taugh.com>
To: ietf-smtp@ietf.org
In-Reply-To: <de6d60415a2e3c9e3ab95690ca71b4e7cae94cf2.camel@aegee.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/bbWoI-U3NSsavI2NpwwSjW_Sty4>
Subject: Re: [ietf-smtp] How to encrypt SMTP?
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Oct 2019 19:00:03 -0000

In article <de6d60415a2e3c9e3ab95690ca71b4e7cae94cf2.camel@aegee.org> you write:
>Hello Viktor,
>
>thanks for your answer.
>
>Why is it common for https-providers to offer both RSA and EC certificates, but it is not common for IMAP or SMTP
>providers to offer EC certificates?  I mean, if EC offers less calculations without sacrificing security, why nobody
>makes use of this?

Probably because the TLS parts of MTAs get less attention than the TLS
part of web browsers and servers.  Everyone uses the same handful of
underlying crypto libraries (opensssl, gnutle, a few others) so in the
MTA it's mostly just tweaking parameters to the library calls.

v2.23.0 | Report a Bug | By Email