Services/Sync/SimplifiedCrypto: Difference between revisions

Services/Sync/SimplifiedCrypto (view source)

257 bytes removed , 26 November 2010

canmove, Confirmed users

725

edits

@@ Line 48: / Line 48: @@
 So long as the salt is available, other clients can apply PBKDF2 to their stored passphrase and the salt to yield the new key without any re-entry or J-PAKE-style key distribution.
-The generated base32 alphanumeric key doesn't actually need to be decoded: it is used as input into hash operations which yield an encryption key and an HMAC key.
-('''Note:''' however, for NSS convenience in the future, we intend to decode it. Still pending.)
 A known fixed string (which includes encryption algo details) and the username are used as input to SHA256-HMAC. The hash operations are chained.
+      let m = Utils.decodeKeyBase32(syncKey);
-    let m = this.keyStr;
-    if (m) {
        // Reuse the hasher.
        let h = Utils.makeHMACHasher();
@@ Line 71: / Line 66: @@
        // Save them.
-       this._encrypt = btoa(enc);    // WeaveCrypto expects it.
+       this._encrypt = btoa(enc);    // WeaveCrypto expects base64
        this._hmac    = hmac;
-    }