IETF Logo Mail Archive

Re: [openpgp] saltpack on OpenPGP message format problems

"Neal H. Walfield" <neal@walfield.org> Wed, 10 February 2016 22:02 UTC

Return-Path: <neal@walfield.org>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB0391B3081 for <openpgp@ietfa.amsl.com>; Wed, 10 Feb 2016 14:02:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level:
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_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 5m-P--hLHrjR for <openpgp@ietfa.amsl.com>; Wed, 10 Feb 2016 14:02:28 -0800 (PST)
Received: from mail.dasr.de (mail.dasr.de [217.69.77.164]) by ietfa.amsl.com (Postfix) with ESMTP id 154EE1B307F for <openpgp@ietf.org>; Wed, 10 Feb 2016 14:02:28 -0800 (PST)
Received: from p50813b37.dip0.t-ipconnect.de ([80.129.59.55] helo=mail.huenfield.org) by mail.dasr.de with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.76) (envelope-from <neal@walfield.org>) id 1aTcq6-0005iU-I4; Wed, 10 Feb 2016 22:02:22 +0000
Received: from grit.huenfield.org ([192.168.20.253]) by mail.huenfield.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <neal@walfield.org>) id 1aTcq5-0006qx-2E; Wed, 10 Feb 2016 23:02:22 +0100
Received: from ip6-localhost.huenfield.org ([::1] helo=grit.huenfield.org.walfield.org) by grit.huenfield.org with esmtp (Exim 4.84) (envelope-from <neal@walfield.org>) id 1aTcq3-0003ni-TN; Wed, 10 Feb 2016 23:02:19 +0100
Date: Wed, 10 Feb 2016 23:02:19 +0100
Message-ID: <87d1s4b4wk.wl-neal@walfield.org>
From: "Neal H. Walfield" <neal@walfield.org>
To: Stephen Paul Weber <singpolyma@singpolyma.net>
In-Reply-To: <20160210213108.GD3090@singpolyma-liberty>
References: <56BB0308.8020504@iang.org> <20160210160641.GA3090@singpolyma-liberty> <87egckbatw.wl-neal@walfield.org> <20160210213108.GD3090@singpolyma-liberty>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (Gojō) APEL/10.8 EasyPG/1.0.0 Emacs/24.5 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset="US-ASCII"
X-SA-Exim-Connect-IP: 192.168.20.253
X-SA-Exim-Mail-From: neal@walfield.org
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 17:06:47 +0000)
X-SA-Exim-Scanned: Yes (on mail.huenfield.org)
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/XrXW-OBb6JYBEk4tpPzCpnyEE5A>
Cc: openpgp@ietf.org, ianG <iang@iang.org>
Subject: Re: [openpgp] saltpack on OpenPGP message format problems
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Feb 2016 22:02:28 -0000

On Wed, 10 Feb 2016 22:31:08 +0100,
Stephen Paul Weber wrote:
> 
> [1  <text/plain; us-ascii (quoted-printable)>]
> > I disagree.  If you are being really paranoid, then you don't want to
> > use OpenPGP from an email client.  Instead, you write your message
> > using something like vi, encrypt it from the command line, and then
> > copy and paste the result into your mail client.  Then you are certain
> > that your mail was encrypted and that you don't accidentally send an
> > unencrypted draft, etc.
> 
> Sure, but then just attach the binary file instead of cut-pasting some
> ASCII stuff.  Same effect.

I still think the copy and paste work flow will lead to less mistakes.
But, of course, if you send the wrong encrypted file to someone, the
she won't be able to read it.

:) Neal

v2.23.0 | Report a Bug | By Email