Bitwarden Completes Third-Party Security Audit
blog.bitwarden.com
Bitwarden Completes Third-Party Security Audit
1–10 of 148 posts
Re: Bitwarden Completes Third-Party Security Audit
#2Re: Bitwarden Completes Third-Party Security Audit
#3Re: Bitwarden Completes Third-Party Security Audit
#4In other news: my todo list now features an item to migrate lastpass -> bitwarden.
(I really love the effort here)
Re: Bitwarden Completes Third-Party Security Audit
#5Re: Bitwarden Completes Third-Party Security Audit
#6> All in all, while the client and backend code are vulnerable to some issues, all of the problems can be easily fixed without a lot of effort. In that sense, Cure53 believes these items of the Bitwarden scope to be fully capable of reaching the desired standards of security in a rather short time. To reiterate, the results of this autumn 2018 assessment are positive for the client and code.
Wondering how they will address the current cryptographic scheme though.
Re: Bitwarden Completes Third-Party Security Audit
#7Previously used Lastpass for 8 years.
So glad to see that it's security taken seriously by the developers!
Re: Bitwarden Completes Third-Party Security Audit
#8Re: Bitwarden Completes Third-Party Security Audit
#9isn't there still a lot more hardening things to do, like moving payment out from vault.bitwarden.com, so that this domain can have a stronger CSP policy? In other news: my todo list now features an item to migrate lastpass -> bitwarden. (I really love the effort here)
[0]: https://help.bitwarden.com/article/import-from-lastpass/
Re: Bitwarden Completes Third-Party Security Audit
#10isn't there still a lot more hardening things to do, like moving payment out from vault.bitwarden.com, so that this domain can have a stronger CSP policy? In other news: my todo list now features an item to migrate lastpass -> bitwarden. (I really love the effort here)