118
edits
Privacy/Features/DOMCryptAPISpec/Latest: Difference between revisions
Jump to navigation
Jump to search
Privacy/Features/DOMCryptAPISpec/Latest (view source)
Revision as of 01:00, 25 August 2011
, 25 August 2011→DOMCrypt Specification
| Line 114: | Line 114: | ||
*Each origin will only have access to the asymmetric private key generated for it. This will minimize the need for any kind of access control dialog for key usage. | *Each origin will only have access to the asymmetric private key generated for it. This will minimize the need for any kind of access control dialog for key usage. | ||
* All the inputs and outputs should be raw, unformatted ArrayBuffers, letting higher-level pure JS wrappers deal with conversion to application data formats until we understand better what higher-level formats would be useful | * All the inputs and outputs should be raw, unformatted ArrayBuffers, letting higher-level pure JS wrappers deal with conversion to application data formats until we understand better what higher-level formats would be useful | ||
== Possible Additions == | |||
<pre class="brush:js;toolbar:false;"> | |||
[Supplemental] | |||
interface Crypto { | |||
readonly attribute CryptoUser user; | |||
}; | |||
</pre> | |||
== References == | == References == | ||