IETF Logo Mail Archive

Re: [openpgp] saltpack on OpenPGP message format problems

Stephen Paul Weber <singpolyma@singpolyma.net> Wed, 10 February 2016 21:31 UTC

Return-Path: <singpolyma@singpolyma.net>
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 D23A31B3006 for <openpgp@ietfa.amsl.com>; Wed, 10 Feb 2016 13:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.003
X-Spam-Level:
X-Spam-Status: No, score=-2.003 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 QP6EHY_1Yk0z for <openpgp@ietfa.amsl.com>; Wed, 10 Feb 2016 13:31:09 -0800 (PST)
Received: from singpolyma.net (singpolyma.net [184.107.182.218]) by ietfa.amsl.com (Postfix) with ESMTP id D0ABB1B3000 for <openpgp@ietf.org>; Wed, 10 Feb 2016 13:31:09 -0800 (PST)
Received: by singpolyma.net (Postfix, from userid 1000) id 643DF26C0007; Wed, 10 Feb 2016 21:31:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=singpolyma.net; s=iweb; t=1455139869; bh=RayflUspNGEua12I/b01hAAJolf6wUAxp39g2vHRLgg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:In-Reply-To; b=P2KYRUsG5CN6zRMLwdhpEdwP6w9Af+E7JD4QIWT/QyzjFe7WU6RFwOPRGe6ZNC142 xq9cR6oIzHUdw4UMJ/DncBaD9H6yxG7tPPZbOLz1Bzd9/o8MA1eMRtXex6zPnsqTbG ts2jyqO8n+vafROmaT2uvpLAEYy1P9/4hYdmN5UE=
Date: Wed, 10 Feb 2016 16:31:08 -0500
From: Stephen Paul Weber <singpolyma@singpolyma.net>
To: "Neal H. Walfield" <neal@walfield.org>
Message-ID: <20160210213108.GD3090@singpolyma-liberty>
References: <56BB0308.8020504@iang.org> <20160210160641.GA3090@singpolyma-liberty> <87egckbatw.wl-neal@walfield.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="P+33d92oIH25kiaB"
Content-Disposition: inline
In-Reply-To: <87egckbatw.wl-neal@walfield.org>
Jabber-ID: singpolyma@singpolyma.net
OpenPGP: id=CE519CDE; url=https://singpolyma.net/public.asc
X-URL: https://singpolyma.net
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <http://mailarchive.ietf.org/arch/msg/openpgp/fIsFmDGbhMBboyxtr1xoTS8cMKE>
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 21:31:11 -0000

>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.

v2.23.0 | Report a Bug | By Email