IETF Logo Mail Archive

Re: [jose] Proposed resolution of header criticality issue

Dick Hardt <dick.hardt@gmail.com> Tue, 12 March 2013 06:38 UTC

Return-Path: <dick.hardt@gmail.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD6CA21F8718 for <jose@ietfa.amsl.com>; Mon, 11 Mar 2013 23:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.376
X-Spam-Level:
X-Spam-Status: No, score=-1.376 tagged_above=-999 required=5 tests=[AWL=-1.424, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, RCVD_IN_PBL=0.905, RCVD_IN_SORBS_DUL=0.877, RDNS_DYNAMIC=0.1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5vZLTnUXEp7G for <jose@ietfa.amsl.com>; Mon, 11 Mar 2013 23:38:41 -0700 (PDT)
Received: from mail-ie0-x235.google.com (mail-ie0-x235.google.com [IPv6:2607:f8b0:4001:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 2334721F86C2 for <jose@ietf.org>; Mon, 11 Mar 2013 23:38:41 -0700 (PDT)
Received: by mail-ie0-f181.google.com with SMTP id 17so5953213iea.12 for <jose@ietf.org>; Mon, 11 Mar 2013 23:38:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:content-type:mime-version:subject:from:in-reply-to:date :cc:content-transfer-encoding:message-id:references:to:x-mailer; bh=XrFkqAPWzc00z2w056CFvEKK/+7/ndNjjaT/fELUEaY=; b=BRTroyz2CKUbB2Mnu7rveJ8LEtMG4nUFt2Atuv/naK+mZGtRUqPG8yXjix+b/kUT7N 6nnjCkZHhToXi/lvrdJq2q3HB5C8c9Ryz+nkUGaCI7228U6nHewwQiy4prXZgbpx1yUH E6ddeHNyErZ2KkDfghLtjXpN+ONacc8kz7koefFE2UJd7l8U6L256cR+fao8iOmrKQPY fB/sNqSOlFiDe4qg5P8XKA5Nhp9s69craKMK6jJKGP1BQXnDMipL1ojTG+4yUH74TcxH 7cSnYYbNZMUkFbL1w1kPV2ogMkqqPm0Z9E9bLkCuz69Se1hjZgzWUp5gt7Xgs7gP0zBT pPCQ==
X-Received: by 10.50.1.198 with SMTP id 6mr10470566igo.0.1363070320808; Mon, 11 Mar 2013 23:38:40 -0700 (PDT)
Received: from [10.0.0.80] (c-24-5-69-173.hsd1.ca.comcast.net. [24.5.69.173]) by mx.google.com with ESMTPS id ew5sm19554249igc.2.2013.03.11.23.38.38 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Mar 2013 23:38:39 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <255B9BB34FB7D647A506DC292726F6E1150B786C1F@WSMSG3153V.srv.dir.telstra.com>
Date: Mon, 11 Mar 2013 23:38:37 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6497528B-758E-4060-B884-29ECFB1DD34E@gmail.com>
References: <513E6A73.1090403@isoc.org> <513E774C.6090605@isoc.org> <0B6EA527-9DE6-4708-A48D-9D2660951F84@gmail.com> <255B9BB34FB7D647A506DC292726F6E1150B786C1F@WSMSG3153V.srv.dir.telstra.com>
To: "Manger, James H" <James.H.Manger@team.telstra.com>
X-Mailer: Apple Mail (2.1499)
Cc: jose@ietf.org
Subject: Re: [jose] Proposed resolution of header criticality issue
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Javascript Object Signing and Encryption <jose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jose>, <mailto:jose-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/jose>
List-Post: <mailto:jose@ietf.org>
List-Help: <mailto:jose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jose>, <mailto:jose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Mar 2013 06:38:41 -0000

Thanks for the clear explanation James. 

On Mar 11, 2013, at 11:08 PM, "Manger, James H" <James.H.Manger@team.telstra.com> wrote:

>> Why must "zip" be understood? Is there a security issue here or just
>> degraded performance? In my current implementations, "zip" does not
>> help me enough to bother with the added complexity and I have not
>> implemented support.
>> 
>> -- Dick
> 
> You don't want to try to interpret compressed data as plain text. That could be a security problem. A tricky person might be able to create, say, a valid JSON value X that compresses to Y that is also valid JSON. If you ignore "zip" you get JOSE-verified Y; if you process "zip" you get JOSE-verified X.
> 
> You might not have to implement "zip" (that is a separate MTI discussion), but your recipient code at least needs to notice when "zip" is present and throw an error (instead of misinterpreting the compressed content).
> 
> --
> James Manger

v2.23.0 | Report a Bug | By Email