- May 3, 2015
- 1,760
I use stickypasword. My brain.exe is not compatible with 200+ different logins and credentials all using different passwords
Bitwarden, simple, free, open source and safe!
yes, it´s simple, free, and open source. But it´s not safe!
Can you explain why it's not safe ?? in what you base??
Content-Security-Policy:
default-src 'self';
script-src 'self' 'sha256-ryoU+5+IUZTuUyTElqkrQGBJXr1brEv6r2CA62WUw8w=' https://js.stripe.com https://js.braintreegateway.com https://www.paypalobjects.com;
style-src 'self' 'unsafe-inline' https://assets.braintreegateway.com https://*.paypal.com; img-src 'self' data: https://icons.bitwarden.net https://*.paypal.com https://www.paypalobjects.com https://q.stripe.com https://haveibeenpwned.com https://www.gravatar.com;
child-src 'self' https://js.stripe.com https://assets.braintreegateway.com https://*.paypal.com https://*.duosecurity.com;
frame-src 'self' https://js.stripe.com https://assets.braintreegateway.com https://*.paypal.com https://*.duosecurity.com;
connect-src 'self' wss://notifications.bitwarden.com https://notifications.bitwarden.com https://cdn.bitwarden.net https://api.pwnedpasswords.com https://twofactorauth.org https://api.stripe.com https://www.paypal.com https://api.braintreegateway.com https://client-analytics.braintreegateway.com https://*.braintree-api.com;
object-src 'self' blob:;
grant_type=password
&username=XY
&password=DkSSVh%2FsNxf6s8qOIO5apW9mQzWit65H99TAZItZMps%3D
&scope=api+offline_access
&client_id=mobile
&DeviceType=Android
&DeviceIdentifier=02efaea0-6d37-4a51-b868-279eab44ab70
&DeviceName=Redmi+Note+4&DevicePushToken=
Webinterface: The problem is that the encryption and decryption of the password database is done by JavaScript. JavaScript and security are two parameters that are mutually exclusive. You could perhaps overlook this, but not by integrating JavaScript code from other domains into the context of the highly sensitive environment.
The content security policy of the Bitwarden web interface is structured as follows:
Code:Content-Security-Policy: default-src 'self'; script-src 'self' 'sha256-ryoU+5+IUZTuUyTElqkrQGBJXr1brEv6r2CA62WUw8w=' https://js.stripe.com https://js.braintreegateway.com https://www.paypalobjects.com; style-src 'self' 'unsafe-inline' https://assets.braintreegateway.com https://*.paypal.com; img-src 'self' data: https://icons.bitwarden.net https://*.paypal.com https://www.paypalobjects.com https://q.stripe.com https://haveibeenpwned.com https://www.gravatar.com; child-src 'self' https://js.stripe.com https://assets.braintreegateway.com https://*.paypal.com https://*.duosecurity.com; frame-src 'self' https://js.stripe.com https://assets.braintreegateway.com https://*.paypal.com https://*.duosecurity.com; connect-src 'self' wss://notifications.bitwarden.com https://notifications.bitwarden.com https://cdn.bitwarden.net https://api.pwnedpasswords.com https://twofactorauth.org https://api.stripe.com https://www.paypal.com https://api.braintreegateway.com https://client-analytics.braintreegateway.com https://*.braintree-api.com; object-src 'self' blob:;
In particular, the script-src line is thought-provoking, since, among other things, the reloading of JavaScript from third-party sources is permitted. With each resource that Bitwarden integrates into the context of the web interface, the site enters into a trust relationship with the respective source or domain. This in turn also means that the actual control over the delivered resource lies solely with the third-party provider. If, however, the third-party provider is compromised or hacked in any way, this can possibly lead to the attacker modifying the resource to be delivered and, for example, a malicious JavaScript code being delivered to the user instead of a harmless one.
Android app: The Android app (version 1.21.0) also includes three trackers:
Google Analytics
Google Firebase Analytics
hockey app
In a practical exam I was able to discover two of these trackers. Immediately after opening the app, data is transferred to Google Analytics and Google Firebase Analytics - regardless of whether the user has agreed or not. While Google Firebase Analytics might still be a failure to deactivate, Google Analytics Tracker was deliberately integrated. In an app context that manages such sensitive data as passwords, trackers have basically lost nothing - such "mistakes" are hard for me to understand. After all, tracking can be deactivated via the options.
Furthermore, I was a bit surprised that my master password obviously goes over the line - albeit in a somehow hashed format [POST Request]:
Code:grant_type=password &username=XY &password=DkSSVh%2FsNxf6s8qOIO5apW9mQzWit65H99TAZItZMps%3D &scope=api+offline_access &client_id=mobile &DeviceType=Android &DeviceIdentifier=02efaea0-6d37-4a51-b868-279eab44ab70 &DeviceName=Redmi+Note+4&DevicePushToken=
Here I would have wished for a separation between authentication and the encryption of the password database. Maybe a master key or something similar is derived from the master password. You would have to have a closer look at the source code.
Source: Kuketz-Blog
Lastpass as my primary and BitWarden as a backup.