This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23500 - Raw AES access?
Summary: Raw AES access?
Status: RESOLVED WONTFIX
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-14 19:51 UTC by Harry Halpin
Modified: 2014-02-24 20:23 UTC (History)
1 user (show)

See Also:

Attachments

Description Harry Halpin 2013-10-14 19:51:12 UTC 
I didn'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
Comment 1 Mark Watson 2014-02-20 20:18:46 UTC 
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.
Comment 2 Mark Watson 2014-02-24 20:23:08 UTC 
As per mailing list discussion and 2/24/14 call.