Re: [jose] Richard Barnes' Discuss on draft-ietf-jose-json-web-algorithms-33: (with DISCUSS and COMMENT)

Brian Campbell <bcampbell@pingidentity.com> Mon, 13 October 2014 11:18 UTC

Return-Path: <bcampbell@pingidentity.com>
X-Original-To: jose@ietfa.amsl.com
Delivered-To: jose@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 359861A1A47 for <jose@ietfa.amsl.com>; Mon, 13 Oct 2014 04:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.578
X-Spam-Level:
X-Spam-Status: No, score=-3.578 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 bVzE5Y-s3Q1Y for <jose@ietfa.amsl.com>; Mon, 13 Oct 2014 04:18:13 -0700 (PDT)
Received: from na3sys009aog126.obsmtp.com (na3sys009aog126.obsmtp.com [74.125.149.155]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AE0E1A1A36 for <jose@ietf.org>; Mon, 13 Oct 2014 04:18:13 -0700 (PDT)
Received: from mail-ig0-f170.google.com ([209.85.213.170]) (using TLSv1) by na3sys009aob126.postini.com ([74.125.148.12]) with SMTP ID DSNKVDu09azRcNITG6OPrZL0Eoj/zCI3Qvrp@postini.com; Mon, 13 Oct 2014 04:18:13 PDT
Received: by mail-ig0-f170.google.com with SMTP id hn15so13371987igb.1 for <jose@ietf.org>; Mon, 13 Oct 2014 04:18:12 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=v43lvKmnQ29/SPPsCcgE9hI0qMmApZs8EdSPoxazqZ8=; b=Cqrn4VKIb6wsMbbnSfQLZKi7reUSHJ/50wjOLno/M4uYC8TQ8w79D2W9GRH+XBdrOU 7/hfQ5QhVMJ5Jm+GVXO2Le5e1R0qNZZo8AnaM/MTB9UDAcnTvzGyjflwtjjLEMG8Tc9/ EIVRUIR4449uypz5lehja3WA/zw0Oc/G56kvtdiF9ervoLvRiITs21PA42cMrQ0yoMnz 3xoO7W+c+3lL9U51JFRdKArR5hwicUs1kwhyAETVKlmnTETJ10WBRf6LodN9Lt7SzWFe 77H9WdqFC4yBUiPgVotx+Mym/8HKU6YQdAzXVNAboQ7Yu66YRbgIHyWJyP7Aer/vmvwp qxTg==
X-Gm-Message-State: ALoCoQmo+pA9Oj3LUPT2jhmX/y4x0UFAfIn8AZPz4+GKubYmE4AHUyQah1/vXwnbqYSksGNYjFfQbOUNw4m4iIWa/BFGC2Nj+U0u6SmBO6a7TU7zroy3qZyAp82bzOojkgD3askN8EL7
X-Received: by 10.50.61.195 with SMTP id s3mr401442igr.40.1413199092837; Mon, 13 Oct 2014 04:18:12 -0700 (PDT)
X-Received: by 10.50.61.195 with SMTP id s3mr401422igr.40.1413199092720; Mon, 13 Oct 2014 04:18:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.12.137 with HTTP; Mon, 13 Oct 2014 04:17:42 -0700 (PDT)
In-Reply-To: <4E1F6AAD24975D4BA5B16804296739439BAFACA8@TK5EX14MBXC286.redmond.corp.microsoft.com>
References: <20141002023617.18602.69709.idtracker@ietfa.amsl.com> <4E1F6AAD24975D4BA5B16804296739439BAF0C49@TK5EX14MBXC286.redmond.corp.microsoft.com> <CAL02cgR6zHZpDHFwdZHvNd7+wHMwraqCtFz-u=Y3Ogfm9M6n3A@mail.gmail.com> <4E1F6AAD24975D4BA5B16804296739439BAFACA8@TK5EX14MBXC286.redmond.corp.microsoft.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Mon, 13 Oct 2014 05:17:42 -0600
Message-ID: <CA+k3eCQHk9KU9cWr3c1yyHbA+Es03-DL1zihbA_qY-FJ24Y5AA@mail.gmail.com>
To: Mike Jones <Michael.Jones@microsoft.com>
Content-Type: multipart/alternative; boundary=047d7bdc05f2eb4f8a05054c0d9c
Archived-At: http://mailarchive.ietf.org/arch/msg/jose/p1aSeHgI_o4nZ_anHXl_zSqe5UQ
Cc: Richard Barnes <rlb@ipv.sx>, "draft-ietf-jose-json-web-algorithms@tools.ietf.org" <draft-ietf-jose-json-web-algorithms@tools.ietf.org>, "jose-chairs@tools.ietf.org" <jose-chairs@tools.ietf.org>, The IESG <iesg@ietf.org>, "jose@ietf.org" <jose@ietf.org>
Subject: Re: [jose] Richard Barnes' Discuss on draft-ietf-jose-json-web-algorithms-33: (with DISCUSS and COMMENT)
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 13 Oct 2014 11:18:15 -0000

Something to de-emphasize RSAES-PKCS1-v1_5 seems like a good idea.

Working in the Java world, OAEP is readily available but I can't really
comment on its deployment beyond that.


On Sat, Oct 11, 2014 at 2:23 PM, Mike Jones <Michael.Jones@microsoft.com>
wrote:

> > From: Richard Barnes [mailto:rlb@ipv.sx]
> > Sent: Friday, October 10, 2014 2:58 PM
> > To: Mike Jones
> > Cc: The IESG; jose-chairs@tools.ietf.org;
> draft-ietf-jose-json-web-algorithms@tools.ietf.org; jose@ietf.org
> > Subject: Re: [jose] Richard Barnes' Discuss on
> draft-ietf-jose-json-web-algorithms-33: (with DISCUSS and COMMENT)
>
> > Thanks for the pointer to 8.3.  I had missed that.  That helps, but
> doesn't resolve the issue.
> > My concern here is that by having RSAES-PKCS1-v1_5 as a REQUIRED
> algorithm, we will encourage the creation of more vulnerable stacks, and
> extend the life of those that already exist.  (Note that this is
> independent of the guidance in RFC 3447.)  Could we compromise on moving
> the requirement level for this algorithm to OPTIONAL, and promoting OAEP to
> REQUIRED?
>
> Rather than Optional, I'd counter-propose to change it to Recommended- and
> changing OAEP to Recommended+.  It's not clear that OAEP is widely enough
> deployed yet to make it REQUIRED.  What do others in the working group
> think?
>