☣️ This is why you should never trust your important information (like passwords!) to proprietary software like @1password.

#OpenSource #FreeSoftware #privacy #security #infosec

🤡 #1Password becomes #spyware:

https://blog.1password.com/privacy-preserving-app-telemetry/

We're changing how we discover and prioritize improvements | 1Password

Learn about a new, privacy-preserving in-app telemetry system that 1Password is trialing with its employees.

1Password Blog
@downey @1password It's a shame. 1Password was such a beautiful application for a long time before they started moving vaults to the cloud and dropping native apps. 👉️ Migrating from 1Password to KeePass, @keepassxc and KeePassium https://keepassium.com/articles/migrating-from-1password-to-keepass-keepassxc-keepassium/
Migrating from 1Password to KeePass, KeePassXC and KeePassium

Learn how to convert your 1Password vault into a KeePass database, switch to self-hosted KeePass ecosystem and own your passwords.

KeePassium
@glamcode @downey @1password @keepassxc no custom field support, safeincloud and enpass are a closer alternative
@cmscy @glamcode @[email protected] @1password You can create any field you want in KeePassXC.
@keepassxc i see it’s under advanced, but i see no option to mark it as additional url, etc. at least it has the option to set it as protected for additional passwords under the same domain(more common use case than one would imagine) @glamcode @1password

@keepassxc

let me explain a bit more, the reason 1password become popular, especially in corpo is because the fields are truly flexible, you can a new entry, imagine like a new wiki page instead of database entry, then add the basic username/password but from there you have the ability to add custom fields and mark what type they are, url, password, text, etc. in keepassxc under advance, sure i can add more text entries and mark them as protected if they are a pass but

@glamcode @1password

@keepassxc no much more, the 2 managers i mentioned while not opensource, they are the closest you can get, bitwarden is out of the question due to not allowing to change the name of the uri entry, and in an environment with multiple domains with the same credentials, ex. a company/school that is a must, so while you can add custom entries in keepassxc, due to the limitations of the keepass database structure, it's not a real alternative

@glamcode @1password