I also made a change and switched to Enpass.
this post was submitted on 26 Oct 2024
27 points (93.5% liked)
Linux and Tech News
1012 readers
1 users here now
This is where all the News about Linux and Linux adjacent things goes. We'll use some of the articles here for the show! You can watch or listen at:
You can also get involved at our forum here on Lemmy:
Or just get the most recent episode of the show here:
founded 1 year ago
MODERATORS
Uh...
Enpass is a freemium password manager and
From wikipedia.
So you switched to a proprietary password manager?
Also:
The Enpass app retains no user data on its company servers,[6][7] instead storing and syncing encrypted password vaults on storage controlled by the end user.
How is this different than keepass/xc, a fully foss solution?
Keypass has worse usability, worse mobile apps, worse syncing across devices.
…thanks again for submitting the concern here. We have made some adjustments to how the SDK code is organized and packaged to allow you to build and run the app with only GPL/OSI licenses included. The sdk-internal package references in the clients now come from a new sdk-internal repository, which follows the licensing model we have historically used for all of our clients (see LICENSE_FAQ.md for more info). The sdk-internal reference only uses GPL licenses at this time. If the reference were to include Bitwarden License code in the future, we will provide a way to produce multiple build variants of the client, similar to what we do with web vault client builds.
The original sdk repository will be renamed to sdk-secrets, and retains its existing Bitwarden SDK License structure for our Secrets Manager business products. The sdk-secrets repository and packages will no longer be referenced from the client apps, since that code is not used there."
With that it appears the situation is now cleared up and should also avoid any user confusion for those using this open-source password management solution.