IETF Logo Mail Archive

Re: [ietf-dkim] Where is the formal definition of DKIM-Signature?

"John R. Levine" <johnl@iecc.com> Thu, 08 February 2018 16:07 UTC

Return-Path: <ietf-dkim-bounces@mipassoc.org>
X-Original-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Delivered-To: ietfarch-ietf-dkim-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF0BA12D7E8 for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Thu, 8 Feb 2018 08:07:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.789
X-Spam-Level:
X-Spam-Status: No, score=-1.789 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1536-bit key) reason="fail (message has been altered)" header.d=iecc.com
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 gJX8s7YFmPnI for <ietfarch-ietf-dkim-archive@ietfa.amsl.com>; Thu, 8 Feb 2018 08:06:59 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (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 2C76F126E64 for <ietf-dkim-archive@ietf.org>; Thu, 8 Feb 2018 08:06:59 -0800 (PST)
Received: from simon.songbird.com (simon.songbird.com [127.0.0.1]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w18G6EX6032384; Thu, 8 Feb 2018 08:06:15 -0800
Authentication-Results: simon.songbird.com; dkim=fail reason="verification failed; unprotected key" header.d=iecc.com header.i=@iecc.com header.b=lhliAkm0; dkim-adsp=none (unprotected policy); dkim-atps=neutral
Received: from gal.iecc.com (gal.iecc.com [64.57.183.53]) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w18G6Buw032368 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <ietf-dkim@mipassoc.org>; Thu, 8 Feb 2018 08:06:12 -0800
Received: (qmail 725 invoked from network); 8 Feb 2018 16:05:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=2d3.5a7c753a.k1802; bh=rHo0OVbwRwkIfMlHfjTdv3/+JH4hd8wzuFlQj5OHoZY=; b=lhliAkm0o58e5IVe/KEfQGM+P60TGEXvuJ13sAU22v7dAESnvTDZUWINd1MMCVpNRLJuWW7kWqr4QXeHZVJnGo0ZHi4auPrlnGkQAt9FKA0xzqxtBiFA0ERYU7/0UlblRCDrEB2gwlVA412PlPipLASUO3p95G5KFnM4U+YAgFwwgTDmau5VDydW+OzX0GQR+L5HV+8Y/opKxHpmG9IREfGhD+LTCpZukiQbYcig7NjqJUaiApjsJ68FFgZs7bdU
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.2/X.509/AEAD) via TCP6; 08 Feb 2018 16:05:14 -0000
Date: Thu, 08 Feb 2018 11:05:13 -0500
Message-ID: <alpine.OSX.2.21.1802081053330.52201@ary.qy>
From: "John R. Levine" <johnl@iecc.com>
To: Dave Crocker <dcrocker@bbiw.net>
In-Reply-To: <95c31903-5181-c6f8-11af-68d492418f46@bbiw.net>
References: <9e7d6a29-cbef-e032-4af9-eb5395071b4d@tana.it> <alpine.OSX.2.21.1802080808160.51311@ary.qy> <95c31903-5181-c6f8-11af-68d492418f46@bbiw.net>
User-Agent: Alpine 2.21 (OSX 202 2017-01-01)
MIME-Version: 1.0
Cc: DKIM List <ietf-dkim@mipassoc.org>
Subject: Re: [ietf-dkim] Where is the formal definition of DKIM-Signature?
X-BeenThere: ietf-dkim@mipassoc.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: IETF DKIM Discussion List <ietf-dkim.mipassoc.org>
List-Unsubscribe: <http://mipassoc.org/mailman/options/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=unsubscribe>
List-Archive: <http://mipassoc.org/pipermail/ietf-dkim/>
List-Post: <mailto:ietf-dkim@mipassoc.org>
List-Help: <mailto:ietf-dkim-request@mipassoc.org?subject=help>
List-Subscribe: <http://mipassoc.org/mailman/listinfo/ietf-dkim>, <mailto:ietf-dkim-request@mipassoc.org?subject=subscribe>
Content-Transfer-Encoding: base64
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Errors-To: ietf-dkim-bounces@mipassoc.org
Sender: ietf-dkim <ietf-dkim-bounces@mipassoc.org>

> Header field name rules are in RFC 5322.  That deals with case sensitivity 
> for field name strings.  Section 1.2.2 provides the basis for knowing whether 
> a defined string is to be parsed in a case sensitive or insensitive manner.

That's right, and all of the fields defined in 5322 have case insensitive 
names, but as far as I can tell, I could define a header like this:

  pickle-header = %d80.111.99.107.108.101 ":" CFWS ( "dill" / "garlic" / "kimchee" )

So this is a pickle-header

  Pickle: dill

but this is not:

  pickle: garlic

I'm not saying any sensible person would do that, but as far as I can 
tell, that's what the spec says.

Regards,
John Levine, johnl@iecc.com, Primary Perpetrator of "The Internet for Dummies",
Please consider the environment before reading this e-mail. https://jl.ly
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html

v2.23.0 | Report a Bug | By Email