<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>26348</bug_id>
          
          <creation_ts>2014-07-16 03:46:51 +0000</creation_ts>
          <short_desc>Allow JWK for PBKDF2</short_desc>
          <delta_ts>2014-09-24 01:22:38 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Web Cryptography</product>
          <component>Web Cryptography API Document</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WONTFIX</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Richard Barnes">rlb</reporter>
          <assigned_to name="Ryan Sleevi">sleevi</assigned_to>
          <cc>public-webcrypto</cc>
    
    <cc>watsonm</cc>
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>108978</commentid>
    <comment_count>0</comment_count>
    <who name="Richard Barnes">rlb</who>
    <bug_when>2014-07-16 03:46:51 +0000</bug_when>
    <thetext>The current spec forbids the use of JWK for import of keys to PBKDF2.  This is unnecessarily restrictive, since a JWK containing only &quot;kty&quot; and &quot;k&quot; elements is valid and equivalent to a raw key.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>108979</commentid>
    <comment_count>1</comment_count>
    <who name="Ryan Sleevi">sleevi</who>
    <bug_when>2014-07-16 03:56:18 +0000</bug_when>
    <thetext>From the point of view of a &quot;JOSE&quot; JWK, I don&apos;t think this is a good idea. JOSE intentionally doesn&apos;t provide PBKDF2 as a valid kty; the key algorithm is only used with the CEK, and associated by alg, not kty. Additionally, rather than store the security parameters on the JWK, they&apos;re part of the JWE&apos;s header parameters.

It&apos;s not &quot;unnecessarily restrictive&quot;, it&apos;s &quot;not defined because it&apos;s undefined for JWK&quot;.

If you feel strongly about this, then I think you&apos;ll need to propose text to the WG for adoption. It certainly seems like it involves new registrations with JWA.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>111960</commentid>
    <comment_count>2</comment_count>
    <who name="Mark Watson">watsonm</who>
    <bug_when>2014-09-22 18:00:36 +0000</bug_when>
    <thetext>I think we should live with the existing text here. If necessary the script can extract the raw key from the JWK itself and import that.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>