W3C home > Mailing lists > Public > public-webcrypto@w3.org > January 2015

[Bug 27814] Section A.2 - the usage mapping of "enc" is incorrect

From: <bugzilla@jessica.w3.org>
Date: Tue, 13 Jan 2015 00:02:08 +0000
To: public-webcrypto@w3.org
Message-ID: <bug-27814-7213-Yu1sOrh3jV@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27814

--- Comment #6 from jimsch <ietf@augustcellars.com> ---
(In reply to Ryan Sleevi from comment #5)
> (In reply to jimsch from comment #4)
> > It is also an "alg" parameter for some JWK - which says that the JWK is to
> > be used only for JWE operations which have the same "alg" value.  That is it
> > can be used to restrict the set of algorithms the key can be used with.
> <snip>
> > And, from a JOSE perspective, this results in an encryption operation even
> > though there are some operations performed which are not encryption in the
> > middle.  Only the composite algorithm is to be considered.
> 
> I'm still a little confused here about how it's relevant to WebCrypto, in as
> much we don't support the composite algorithms.
> 

A JOSE application retrieves a key set from a url.  The key set looks like:

{"keys":[ {"kty":"EC", "use":"enc", ... },
          {"kty":"EC", "use":"sig", ... }]}

In this case the use parameter is used to distinguish between which keys are to
be used to verify signatures and which are to be used for encrypting messages.
If there is an attempt by the JOSE application to import the first key, it will
fail because of the use field.  The second will work just fine.  

Support of JOSE is one of the documented use cases.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 13 January 2015 00:02:10 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 January 2015 00:02:10 UTC