Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passphrase Support for e2e backups #786

Merged
merged 6 commits into from
Nov 21, 2018

Conversation

dbkr
Copy link
Member

@dbkr dbkr commented Nov 20, 2018

@dbkr dbkr requested a review from a team November 20, 2018 16:24
Copy link
Member

@turt2live turt2live left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM assuming the documentation also gets updated

src/client.js Outdated
* @param {string} password Passphrase string that can be entered by the user
* when restoring the backup as an alternative to entering the recovery key.
* Optional.
*
* @returns {object} Object that can be passed to createKeyBackupVersion and
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this now returns a promise, not an object.

Copy link
Member Author

@dbkr dbkr Nov 21, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hmm, I was assuming the promise was implicit for async functions, but the convention seem to be to put it explicitly.

limitations under the License.
*/

export function randomString(len) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fwiw there's libraries for this if we want to avoid maintaining this sort of thing. https://www.npmjs.com/package/random-string for example

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants