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

Add browser.secureStorage proposal #167

Merged
merged 5 commits into from
Mar 9, 2022
Merged

Conversation

oliverdunk
Copy link
Member

This adds the proposal from #154 to a new proposals/ folder in the repository. As discussed at the end of the last meeting, my hope is that this makes it easier to collaborate on the proposal while also providing us with a commit history and issue tracker that we can use while moving this forward as a community.

For now, this is very close to a direct port from the shared document. I plan to start making more changes in future PRs.

proposals/secure-storage.md Outdated Show resolved Hide resolved
Copy link
Member

@dotproto dotproto left a comment

Choose a reason for hiding this comment

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

Bikeshedding in champion name formatting aside, I think this is in a good state to merge & iterate on.


This proposal is drafted by the team at 1Password. Our [extension](https://chrome.google.com/webstore/detail/1password-%E2%80%93-password-mana/aeblfdkhhhdcdjpifhhbdiojplfjncoa?hl=en) is available for Chrome, Firefox, Safari and Edge and has more than 2M weekly active users in the Chrome Web Store alone. We would be quick to implement this in conjunction with or in place of our current Native Messaging solution.

The Dashlane browser extension, also a password manager with over 4M weekly active users in the Chrome Web Store, currently provides a remember me and biometric authentication feature in its extension to make repeated authentication easier. They would also be very quick to implement this in place of their solution which requires a network connection, as they don’t leverage a native application to interface with native storage.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Do we have a public comment of someone from Dashlane supporting this proposal? If not, perhaps better to leave this for a later PR they could submit.

Copy link
Member Author

@oliverdunk oliverdunk Mar 9, 2022

Choose a reason for hiding this comment

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

@bradcush reached out out-of-band and shared this quote which he was happy for us to use in the proposal. I'm fairly sure he's happy with it being included here but I'll ask if he can drop an approval so we have everything documented in one place.

Copy link

Choose a reason for hiding this comment

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

This quote is good for us, confirming here publicly on behalf of Dashlane, thanks!

@dotproto dotproto merged commit c7b420a into w3c:main Mar 9, 2022
github-actions bot added a commit that referenced this pull request Mar 9, 2022
SHA: c7b420a
Reason: push, by @dotproto

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@Rob--W Rob--W added the topic: secure storage Related to the secureStorage API proposal label Mar 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: secure storage Related to the secureStorage API proposal
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants