ISSUE-26: Remove references to ISSUE-26.
By virtue of removing KeyStorage, the nature of origin-shared keys disappears.
Future sources of Key objects may introduce their own sets of concerns regarding
origin sharing, but those should be addressed when they are specified. For now,
Key objects follow the origin policy of the existing storage mechanisms.
--- a/spec/Overview-WebCryptoAPI.xml Mon Dec 03 17:17:11 2012 -0800
+++ b/spec/Overview-WebCryptoAPI.xml Mon Dec 03 17:17:20 2012 -0800
@@ -1370,12 +1370,6 @@
<div class="ednote">
<ul>
<li>
- <a href="http://www.w3.org/2012/webcrypto/track/issues/26">ISSUE-26</a>:
- When generating, importing, or deriving a key, should it be possible to specify
- multiple origins that the key is automatically authorized for, beyond the
- current origin executing the script?
- </li>
- <li>
<a href="https://www.w3.org/2012/webcrypto/track/issues/35">ISSUE-35</a>:
There is an open question as to how the API should support key wrap and unwrap
operations. Should they be distinct operations, independent from key import/export,
@@ -1678,11 +1672,6 @@
<div class="ednote">
<ul>
<li>
- <a href="https://www.w3.org/2012/webcrypto/track/issues/26">ISSUE-26</a>:
- Should callers be allowed to specify a list of origins to authorized the
- key to be shared with?
- </li>
- <li>
<a href="https://www.w3.org/2012/webcrypto/track/issues/16">ISSUE-16</a>:
Should callers be able to specify key lifetime?
</li>
--- a/spec/Overview.html Mon Dec 03 17:17:11 2012 -0800
+++ b/spec/Overview.html Mon Dec 03 17:17:20 2012 -0800
@@ -1366,12 +1366,6 @@
<div class="ednote"><div class="ednoteHeader">Editorial note</div>
<ul>
<li>
- <a href="http://www.w3.org/2012/webcrypto/track/issues/26">ISSUE-26</a>:
- When generating, importing, or deriving a key, should it be possible to specify
- multiple origins that the key is automatically authorized for, beyond the
- current origin executing the script?
- </li>
- <li>
<a href="https://www.w3.org/2012/webcrypto/track/issues/35">ISSUE-35</a>:
There is an open question as to how the API should support key wrap and unwrap
operations. Should they be distinct operations, independent from key import/export,
@@ -1674,11 +1668,6 @@
<div class="ednote"><div class="ednoteHeader">Editorial note</div>
<ul>
<li>
- <a href="https://www.w3.org/2012/webcrypto/track/issues/26">ISSUE-26</a>:
- Should callers be allowed to specify a list of origins to authorized the
- key to be shared with?
- </li>
- <li>
<a href="https://www.w3.org/2012/webcrypto/track/issues/16">ISSUE-16</a>:
Should callers be able to specify key lifetime?
</li>