Privacy/Features/DOMCryptAPI/UseCases: Difference between revisions

 
(One intermediate revision by the same user not shown)
Line 40: Line 40:
SHA 256 hashes are handy for storing passwords and generating checksums (among other uses)
SHA 256 hashes are handy for storing passwords and generating checksums (among other uses)


Example code uses the hashing API: '''window.crypto.hash.*'''
Example code uses the hashing API, using the constructor '''window.crypto.hash'''
 
[Constructor(in DOMString algorithm)]
08.interface CryptoHash {
09.void append(in ArrayBuffer data);
10.ArrayBuffer finish();
11.};


<pre class="brush:js;toolbar:false;">
<pre class="brush:js;toolbar:false;">
Line 64: Line 58:
// Another idea: generating a file checksum in conjunction with the FileAPI
// Another idea: generating a file checksum in conjunction with the FileAPI
</pre>
</pre>
=== Identity in the Browser ===
We will need both a chrome-privileged and content Crypto API for generating keypairs and hashing data. See [[Identity/Verified_Email_Protocol/Latest]]


== New Ideas ==
== New Ideas ==
564

edits