IETF Logo Mail Archive

Re: [lamps] WG Last Call: draft-ietf-lamps-e2e-mail-guidance-08

Bernie Hoeneisen <bernie@ietf.hoeneisen.ch> Fri, 16 June 2023 07:59 UTC

Return-Path: <bernie@ietf.hoeneisen.ch>
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 7CA96C151988 for <spasm@ietfa.amsl.com>; Fri, 16 Jun 2023 00:59:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iUOqg_U7MNDi for <spasm@ietfa.amsl.com>; Fri, 16 Jun 2023 00:59:24 -0700 (PDT)
Received: from softronics.hoeneisen.ch (softronics.hoeneisen.ch [IPv6:2a01:4f8:c0c:15fc::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F40CC151985 for <spasm@ietf.org>; Fri, 16 Jun 2023 00:59:23 -0700 (PDT)
Received: from localhost ([127.0.0.1]) by softronics.hoeneisen.ch with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <bernie@ietf.hoeneisen.ch>) id 1qA4MY-0017W7-UX; Fri, 16 Jun 2023 09:59:18 +0200
Date: Fri, 16 Jun 2023 09:59:18 +0200
From: Bernie Hoeneisen <bernie@ietf.hoeneisen.ch>
X-X-Sender: bhoeneis@softronics.hoeneisen.ch
To: Seo Suchan <tjtncks@gmail.com>
cc: IETF LAMPS WG <spasm@ietf.org>
In-Reply-To: <CB33E08A-5575-4041-918E-468A3F184DCE@gmail.com>
Message-ID: <alpine.DEB.2.22.394.2306160954180.194482@softronics.hoeneisen.ch>
References: <CDB2F6AA-3034-4ECD-A433-F197825BA043@vigilsec.com> <406af10d-efa1-0bd4-0600-65b2f3e6ac25@lear.ch> <CB33E08A-5575-4041-918E-468A3F184DCE@gmail.com>
User-Agent: Alpine 2.22 (DEB 394 2020-01-19)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="8323329-1652548580-1686902358=:194482"
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Mail-From: bernie@ietf.hoeneisen.ch
X-SA-Exim-Scanned: No (on softronics.hoeneisen.ch); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/YdfMmp_ppwFWWZ4RqnHKGe7Wy8g>
Subject: Re: [lamps] WG Last Call: draft-ietf-lamps-e2e-mail-guidance-08
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 16 Jun 2023 07:59:28 -0000

Hi Seo

Just for your information: pEp Foundation has specified and implemented 
such a private key synchronization feature for some time already; though 
so far only covering PGP keys:

   https://datatracker.ietf.org/doc/draft-pep-keysync/

Best,
  Bernie

--

http://ucom.ch/
Modern Telephony Solutions and Tech Consulting for Internet Technology


On Fri, 16 Jun 2023, Seo Suchan wrote:

> I think more important thing is syncing the keys, because if one use acme to get smime cert by acme from multiple device with ACME 
> now you have multiple public key and you can't read the reply of your mail sent by phone on PC, because it doesn't have priv key on
> your phone

v2.23.0 | Report a Bug | By Email