IETF Logo Mail Archive

Re: [jose] Draft describing encrypting JWK key representations, with JWE

"Ryan Sleevi" <ryan-ietf@sleevi.com> Sat, 16 March 2013 20:14 UTC

Return-Path: <ryan-ietf@sleevi.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 6421B21F874A for <jose@ietfa.amsl.com>; Sat, 16 Mar 2013 13:14:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 S2FYXGsYmXVd for <jose@ietfa.amsl.com>; Sat, 16 Mar 2013 13:14:16 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (mailbigip.dreamhost.com [208.97.132.5]) by ietfa.amsl.com (Postfix) with ESMTP id C20C621F8718 for <jose@ietf.org>; Sat, 16 Mar 2013 13:14:16 -0700 (PDT)
Received: from homiemail-a88.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTP id 6C601264058; Sat, 16 Mar 2013 13:14:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sleevi.com; h=message-id :in-reply-to:references:date:subject:from:to:cc:reply-to :mime-version:content-type:content-transfer-encoding; s= sleevi.com; bh=aOGZdWlZA2SGq3u57DkrB2X0if4=; b=Ai50mV2oqJQwVM9U1 863O7J80RDusagN0NWbeSPVT3ynFxQeAdbi+vQBaDZe/Q7OVRw2d4fKLJKAiHBaX EXHJDdoQImL1dO8yfqlhpYzXnYqc3iNY+BgeP0VAD8ytiy/HwEtPSELkDAttrZv/ 9WYr5elh5hNp9RGR+nM1rq35lQ=
Received: from webmail.dreamhost.com (caiajhbihbdd.dreamhost.com [208.97.187.133]) (Authenticated sender: ryan@sleevi.com) by homiemail-a88.g.dreamhost.com (Postfix) with ESMTPA id 2186D264057; Sat, 16 Mar 2013 13:14:16 -0700 (PDT)
Received: from 216.3.101.62 (proxying for 216.3.101.62) (SquirrelMail authenticated user ryan@sleevi.com) by webmail.dreamhost.com with HTTP; Sat, 16 Mar 2013 13:14:16 -0700
Message-ID: <c7f88782a15ccfc55c2919aba0aece23.squirrel@webmail.dreamhost.com>
In-Reply-To: <6769e08f-8bae-41de-a723-409f7bfae4f2@email.android.com>
References: <mailman.4019.1363356696.3432.cfrg@irtf.org> <51433B12.1020703@gmail.com> <4E1F6AAD24975D4BA5B168042967394367526568@TK5EX14MBXC284.redmond.corp.microsoft.com> <CAL02cgQ8=yKwArwvR228Z=xi0N3U6yvoOHt6M-3EuCD_HYkyww@mail.gmail.com> <4E1F6AAD24975D4BA5B168042967394367526789@TK5EX14MBXC284.redmond.corp.microsoft.com> <CAL02cgRbh7EYLwp01t0yMMPHbhtVsQjY8379YF9_gRgGeO08eQ@mail.gmail.com> <8B4C063947CD794BB6FF90C78BAE9B321EFD5DFC@IMCMBX04.MITRE.ORG> <07c801ce21ab$f63d74b0$e2b85e10$@augustcellars.com> <6769e08f-8bae-41de-a723-409f7bfae4f2@email.android.com>
Date: Sat, 16 Mar 2013 13:14:16 -0700
From: Ryan Sleevi <ryan-ietf@sleevi.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
User-Agent: SquirrelMail/1.4.21
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Sat, 16 Mar 2013 19:11:10 -0700
Cc: "'Peck, Michael A'" <mpeck@mitre.org>, 'Richard Barnes' <rlb@ipv.sx>, Jim Schaad <ietf@augustcellars.com>, cfrg@irtf.org, 'Mike Jones' <michael.jones@microsoft.com>, jose@ietf.org
Subject: Re: [jose] Draft describing encrypting JWK key representations, with JWE
X-BeenThere: jose@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ryan-ietf@sleevi.com
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: Sat, 16 Mar 2013 20:14:17 -0000

On Fri, March 15, 2013 12:45 pm, Yaron Sheffer wrote:
>  no way to generate a strong key in JavaScript. So you also need a way to
>  use a key directly. But I'm by no means a JOSE expert, they may have
>  different assumptions.
>
>  Thanks, Yaron

window.crypto.getRandomValues() ?

Already implemented today by WebKit and Firefox, as part of the W3C Web
Cryptography API -
https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html

v2.23.0 | Report a Bug | By Email