ISSUE-46: Make the AES-GCM IV mandatory. Further discussion about whether to fix it at 96-bytes is needed.
--- a/spec/Overview-WebCryptoAPI.xml Mon Aug 05 12:42:40 2013 -0700
+++ b/spec/Overview-WebCryptoAPI.xml Mon Aug 05 12:42:41 2013 -0700
@@ -3069,7 +3069,7 @@
<x:codeblock language="idl">
dictionary <dfn id="dfn-AesGcmParams">AesGcmParams</dfn> : <a href="#dfn-Algorithm">Algorithm</a> {
<span class="comment">// The initialization vector to use. May be up to 2^56 bytes long.</span>
- CryptoOperationData? iv;
+ CryptoOperationData iv;
<span class="comment">// The additional authentication data to include.</span>
CryptoOperationData? additionalData;
<span class="comment">// The desired length of the authentication tag. May be 0 - 128.</span>
--- a/spec/Overview.html Mon Aug 05 12:42:40 2013 -0700
+++ b/spec/Overview.html Mon Aug 05 12:42:41 2013 -0700
@@ -3078,7 +3078,7 @@
<div class="block"><div class="blockTitleDiv"><span class="blockTitle">IDL</span></div><div class="blockContent"><pre class="code"><code class="idl-code">
dictionary <dfn id="dfn-AesGcmParams">AesGcmParams</dfn> : <a href="#dfn-Algorithm">Algorithm</a> {
<span class="comment">// The initialization vector to use. May be up to 2^56 bytes long.</span>
- CryptoOperationData? iv;
+ CryptoOperationData iv;
<span class="comment">// The additional authentication data to include.</span>
CryptoOperationData? additionalData;
<span class="comment">// The desired length of the authentication tag. May be 0 - 128.</span>