<?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>23500</bug_id>
          
          <creation_ts>2013-10-14 19:51:12 +0000</creation_ts>
          <short_desc>Raw AES access?</short_desc>
          <delta_ts>2014-02-24 20:23:08 +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>PC</rep_platform>
          <op_sys>Linux</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="Harry Halpin">hhalpin</reporter>
          <assigned_to name="Ryan Sleevi">sleevi</assigned_to>
          <cc>watsonm</cc>
          
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>94689</commentid>
    <comment_count>0</comment_count>
    <who name="Harry Halpin">hhalpin</who>
    <bug_when>2013-10-14 19:51:12 +0000</bug_when>
    <thetext>I didn&apos;t see access to Raw-AES. There are cases where that is
    needed, e.g. for implementing unsupported modes such as SIV and FFX.

    (Dan Boneh)

    http://lists.w3.org/Archives/Public/public-webcrypto/2013Sep/0055.html</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>100995</commentid>
    <comment_count>1</comment_count>
    <who name="Mark Watson">watsonm</who>
    <bug_when>2014-02-20 20:18:46 +0000</bug_when>
    <thetext>From Jim Schaad:

Take #2 on this issue.
 
Looking at things last night, as long as we don’t have a streaming mode of operation, it does not appear that using a ECB mode is going to be any more efficient than using either CBC or CTR as the basis for building something like an SIV mode.  Since one is going to need to create a new encrypt Promise for each block in order to chain things together.
 
Since this means that currently the only way to  be use ECB mode in an efficient manner is to use it as ECB, I would say that we should not include it.  It might however be worth having a note about how to use CTR mode to build new modes in the future in script.  
 
This decision would then be re-visited when we have streaming as a primitive operation.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>101268</commentid>
    <comment_count>2</comment_count>
    <who name="Mark Watson">watsonm</who>
    <bug_when>2014-02-24 20:23:08 +0000</bug_when>
    <thetext>As per mailing list discussion and 2/24/14 call.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>