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

One keypair per domain? #10

Open
rekado opened this issue Jun 28, 2013 · 1 comment
Open

One keypair per domain? #10

rekado opened this issue Jun 28, 2013 · 1 comment

Comments

@rekado
Copy link
Contributor

rekado commented Jun 28, 2013

Currently, only one keypair is stored per profile. Any page could trigger window.mozCipher.pk.generateKeyPair and thus overwrite the stored key, meaning that the user will lose access to whatever encrypted data had previously been encrypted under the user's public key.

Does it make sense to instead store one keypair for each domain, thereby restricting write access to the keypair?

(How does the Web Crypto API intend to deal with this?)

@daviddahl
Copy link
Owner

nulltxt handles this better: you can create as many keypairs per domain as you would like, each is accessed via a unique ID.

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

No branches or pull requests

2 participants