web/cryptpad
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

initialize newly registered users with a v2 drive hash

Browse Source
This commit is contained in:
ansuz 2018-07-16 17:08:35 +02:00
parent ed881840cd
commit 8a18698c03
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
customize.dist/login.js
View File

@ -72,7 +72,9 @@ define([
opt.channel64 = Util.hexToBase64(channelHex); opt.channel64 = Util.hexToBase64(channelHex);
// XXX why don't we generate a v2 ? // we still generate a v1 hash because this function needs to deterministically
// derive the same values as it always has. New accounts will generate their own
// userHash values
opt.userHash = '/1/edit/' + [opt.channel64, opt.keys.editKeyStr].join('/') + '/'; opt.userHash = '/1/edit/' + [opt.channel64, opt.keys.editKeyStr].join('/') + '/';
return opt; return opt;
@ -278,7 +280,8 @@ define([
} else { } else {
console.log("allocating random bytes for a new user object"); console.log("allocating random bytes for a new user object");
opt = allocateBytes(Nacl.randomBytes(Exports.requiredBytes)); opt = allocateBytes(Nacl.randomBytes(Exports.requiredBytes));
userHash = opt.userHash; // create a random v2 hash, since we don't need backwards compatibility
userHash = '/drive/#' + Hash.createRandomHash('drive');
} }
// according to the location derived from the credentials which you entered // according to the location derived from the credentials which you entered