Re: [openpgp] A way to securely define cleartext signature charset

Marcus Brinkmann <marcus.brinkmann@ruhr-uni-bochum.de> Sat, 08 September 2018 14:43 UTC

Return-Path: <marcus.brinkmann@ruhr-uni-bochum.de>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36366128CFD for <openpgp@ietfa.amsl.com>; Sat, 8 Sep 2018 07:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ruhr-uni-bochum.de
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 Hs0aE5B4_Sns for <openpgp@ietfa.amsl.com>; Sat, 8 Sep 2018 07:43:29 -0700 (PDT)
Received: from out2.mail.ruhr-uni-bochum.de (out2.mail.ruhr-uni-bochum.de [IPv6:2a05:3e00:c:1001::8693:2ae5]) (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 08430126CC7 for <openpgp@ietf.org>; Sat, 8 Sep 2018 07:43:29 -0700 (PDT)
Received: from mx2.mail.ruhr-uni-bochum.de (localhost [127.0.0.1]) by out2.mail.ruhr-uni-bochum.de (Postfix mo-ext) with ESMTP id 426xrG43fsz4yBS for <openpgp@ietf.org>; Sat, 8 Sep 2018 16:43:26 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ruhr-uni-bochum.de; s=mail-2017; t=1536417806; bh=dR0NFezEe3GC7qM8NDffzY9v6XVP21oVuWgdxV1IOEg=; h=Subject:To:References:From:Date:In-Reply-To:From; b=Tu5RnLAOf5b4Fbl0z+c2U6CMk/CWqxGFVBpc6diQvSeo4AgN0ZtQzGbJmAme8vtCI o/RMn/9dO11/Of7e+5pur2LUHv7bS3MZutbKDJ1QnH59JnfIphHhVdhB3vN4m0hXkJ aV0/xCUsA2W75FN7MItSTYFgDovJCauW33BvLhN4=
Received: from out2.mail.ruhr-uni-bochum.de (localhost [127.0.0.1]) by mx2.mail.ruhr-uni-bochum.de (Postfix idis) with ESMTP id 426xrG3Bbfz4yDp for <openpgp@ietf.org>; Sat, 8 Sep 2018 16:43:26 +0200 (CEST)
X-Envelope-Sender: <marcus.brinkmann@ruhr-uni-bochum.de>
X-RUB-Notes: Internal origin=134.147.42.227
Received: from mail1.mail.ruhr-uni-bochum.de (mail1.mail.ruhr-uni-bochum.de [134.147.42.227]) by out2.mail.ruhr-uni-bochum.de (Postfix mi-int) with ESMTP id 426xrG0Zx7z4yBS for <openpgp@ietf.org>; Sat, 8 Sep 2018 16:43:25 +0200 (CEST)
Received: from [192.168.142.139] (p4FE3F0F0.dip0.t-ipconnect.de [79.227.240.240]) by mail1.mail.ruhr-uni-bochum.de (Postfix) with ESMTPSA id 426xrF4mCqzyW8 for <openpgp@ietf.org>; Sat, 8 Sep 2018 16:43:25 +0200 (CEST)
To: openpgp@ietf.org
References: <1803390.QxyNr08ExB@esus>
From: Marcus Brinkmann <marcus.brinkmann@ruhr-uni-bochum.de>
Openpgp: preference=signencrypt
Message-ID: <e7480382-f480-05f2-e525-4f4e36f96433@ruhr-uni-bochum.de>
Date: Sat, 08 Sep 2018 16:43:25 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <1803390.QxyNr08ExB@esus>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: clamav-milter 0.99.4 at mail1.mail.ruhr-uni-bochum.de
X-Virus-Status: Clean
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/PwdKRN4C7WeD3rmU5_0Q4KkIZXs>
Subject: Re: [openpgp] A way to securely define cleartext signature charset
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 08 Sep 2018 14:43:31 -0000

Why not a hashed signature subpacket?

On 09/07/2018 03:52 PM, Andre Heinecke wrote:> Hi,
>
> today I struggled for several hours with "charset guessing" code, that
handles
> cleartext signatures in outlook and I thought that maybe this
situation could
> be improved a bit in the future?
>
> I dislike cleartext signatures as much as the next guy (probably more
;-) ).
> The points made in [1] are valid and such messages should not be used.
> But realistically I think that they won't go away.
>
> My idea would be to define that after the Hash: header and the blank line
> (which starts the hashing) that there can be:
>
> Optionally a "Charset" Armor Header followed by one blank line,
> both included in the message digest.
>
> So a message like:
>
> Charset: UTF-8
>
> This is än example mässäge.
>
>
> An rfc4880 implementation would just show:
> ----
> Charset: UTF-8
>
> This is än example mässäge.
> ----
>
> Ok that is slightly ugly but it's informative and the signature will
still be
> verified correctly.
> An rfc4880bis application could evaluate the header and omit it in the
output.
>
>
> Attached is a patch to the draft.
>
>
> Best Regards,
> Andre
>
>
> 1: https://dkg.fifthhorseman.net/notes/inline-pgp-harmful/
>
>
>
> _______________________________________________
> openpgp mailing list
> openpgp@ietf.org
> https://www.ietf.org/mailman/listinfo/openpgp
>