After this and the few hiccups I’ve had with Bitwarden on Linux (official snap in part still relies on Ubuntu 18.04 libraries and still defaults to X11, not great for security focused app), I’ve decided to give Proton a shot. Went for 2 year unlimited plan, so I hope they don’t do anything stupid in that time.
That being said, I’m not hating on Bitwarden. Based on what one of the developers said, this seems to be an oversight from their side that they should hopefully address. This is just my excuse to try out the Proton suite based on their strong focus on privacy and security, albeit with a hefty cost (and somewhat scummy strategy of listing prices as monthly but are actually paid annually, and choosing the actually monthly options are much more expensive).
I’m similarly testing Proton at the moment.
I tried it at launch, and it was…less than impressive. It worked, but was lacking some features (the details of which I don’t quite remember) and they didn’t have a separate password for Pass vs the rest of their app suite which was a deal breaker for me (which of course they have now).
Testing it now, I’m liking the experience better than Bitwarden overall. There’s some idiosyncrasies between the two I prefer over the other, but nothing deal breaking.
I haven’t found a reason to not switch over, other than the “all eggs in one basket” argument, which is valid but I think I’m OK with.
Yes. Just use Bitwarden’s export feature. Export as an unencrypted json file and you can import that into Proton Pass. I had no issues.
For extra safety, you can export the unencrypted json file to /dev/shm. This is a ram disk so you don’t save all your passwords unencrypted to disk (though this matters less if you use an encrypted disk).
After this and the few hiccups I’ve had with Bitwarden on Linux (official snap in part still relies on Ubuntu 18.04 libraries and still defaults to X11, not great for security focused app), I’ve decided to give Proton a shot. Went for 2 year unlimited plan, so I hope they don’t do anything stupid in that time.
That being said, I’m not hating on Bitwarden. Based on what one of the developers said, this seems to be an oversight from their side that they should hopefully address. This is just my excuse to try out the Proton suite based on their strong focus on privacy and security, albeit with a hefty cost (and somewhat scummy strategy of listing prices as monthly but are actually paid annually, and choosing the actually monthly options are much more expensive).
I’m similarly testing Proton at the moment. I tried it at launch, and it was…less than impressive. It worked, but was lacking some features (the details of which I don’t quite remember) and they didn’t have a separate password for Pass vs the rest of their app suite which was a deal breaker for me (which of course they have now).
Testing it now, I’m liking the experience better than Bitwarden overall. There’s some idiosyncrasies between the two I prefer over the other, but nothing deal breaking.
I haven’t found a reason to not switch over, other than the “all eggs in one basket” argument, which is valid but I think I’m OK with.
I haven’t looked into it but since you have, is it easy to move your vault over?
Yes. Just use Bitwarden’s export feature. Export as an unencrypted json file and you can import that into Proton Pass. I had no issues.
For extra safety, you can export the unencrypted json file to /dev/shm. This is a ram disk so you don’t save all your passwords unencrypted to disk (though this matters less if you use an encrypted disk).