keepassxc
pass-import
keepassxc | pass-import | |
---|---|---|
525 | 405 | |
19,789 | 783 | |
2.7% | - | |
9.1 | 8.1 | |
1 day ago | 26 days ago | |
C++ | Python | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
keepassxc
-
Safari 18 will automatically transition users to passkeys [video]
Here's a great github discussion about passkey plaintext exports.
Apparently, the FIDO alliance is considering adding an attestation feature that would allow websites to block various passkey implementations:
https://github.com/keepassxreboot/keepassxc/issues/10407#iss...
e.g., they could block ones that allow exports, or they could block ones that are FOSS. To their credit, it looks like Apple's throwing their weight around to prevent such blocking from being technically possible.
The more I hear about this standard, the more concerned I become.
- Debian removes KeePassXC browser integration
-
The new APT 3.0 solver
https://github.com/keepassxreboot/keepassxc/issues/10725
-
KeePassXC Debian maintainer has removed all network features
>UPSTREAM THEMSELVES decided not to include in default/recommended build instructions
This is false, or at the very least misleading. It doesn't take much to go on the repository and give a closer look instead of repeating "what other said". Kwpolska already wrote it in this thread, -DWITH_XC_ALL (the flag that's been turned OFF in the original Debian package rules) is explicitly called in the build instructions, and not only there but also one release tool [1] and snap config [2]. This is merely how the project manages its build configuration, with specific flags turned off and one master toggle enabled by default (or expected to be passed to cmake/bash release tool). Same thing for the ppa packaging. [3]
0. https://github.com/keepassxreboot/keepassxc/blob/develop/INS...
1. https://github.com/keepassxreboot/keepassxc/blob/da90319d2d0...
2. https://github.com/keepassxreboot/keepassxc/blob/da90319d2d0...
3. https://github.com/keepassxreboot/keepassxc-packaging/blob/9...
- Debian Sid No-Feature KeePassXC Package
- Passkey Implementation: Misconceptions, pitfalls and unknown unknowns
- KeePassXC Issue: [Passkeys] should never be exported in clear text
- Authy to sunset EOL end of March 19, 2024 (originally August 2024)
-
I Stopped Using Passwords. It's Great–and a Total Mess
KeepassXC supports exporting, but i don't think it is released in a stable version / to the public yet:
https://github.com/keepassxreboot/keepassxc/pull/8825
-
Ask HN: Best Password Manager without cloud login?
If you use KeePass, make sure you use the KeePassXC variant. KeePass is dead.
https://keepassxc.org/
pass-import
- Forget LastPass: Apple unveils 'Passwords' manager app at WWDC 2024
-
macOS Sonoma silently enabled iCloud Keychain despite my precautions
I fully agree.
> thinking people can run their own crypto better than they can
Running or developing ?
You can probably run something like Password Store [1] fairly secure, though you still have to trust the operating system not to leak your secrets, and it turns out that today, regardless of your choice, all major operating systems more or less synchronize your data to the cloud.
I know Linux doesn't do it (Ubuntu tried some Amazon partnership once), but Linux is a poor match for many workplaces where Windows or MacOS are kings. Yes, you can run VSCode (or Vim/Emacs or whatever) on Linux, but running Photoshop, Fusion365 or various other business tools is not as "easy" as on Windows/MacOS, and in the end a company only has so many IT support staffers.
[1]: https://www.passwordstore.org/
- End of Life for Twilio Authy Desktop App
-
I Know What Your Password Was Last Summer
> I always tell these people to just sign up for a password manager and they always resist and say no. I must be missing something obvious.
Maybe they don't want to be relying on a random third-party for all their passwords?
Rather than getting them to sign up for a password manager, what about getting them to install a password manager? I use https://www.passwordstore.org/ - it encrypts your passwords with GPG, and shares the storage via a Git repository for synchronisation between different machines.
-
Command Line Interface Guidelines
That way you can delegate the password handling to another program, e.g. a password manager like pass(1) (https://www.passwordstore.org/) or some interactive graphical prompt.
-
Passit: Open-Source Password Manager
I want to move to something compatible with https://www.passwordstore.org/ - an open standard for keeping your passwords in a folder encrypted with OpenPGP.
The problem is that I'm nervous to give an unknown Android app and browser plugin total control of my passwords and access to my github account when I don't have time to review it's code properly. I have a bit more trust ing the command line tools, but I'd like to be sure that more people are looking at the code before I trust my life to it.
-
Ask HN: Best Password Manager without cloud login?
> Create a system or pattern based on url or brand and mentally hash it into a password.
Doesn't sound very secure. Also when you realize that you anyway have to trust cryptography, I believe it starts making a lot of sense to have an actual cryptographic key and encrypt it with one good random password you learn by heart.
I use pass https://www.passwordstore.org/, which encrypts my passwords with my GPG key, which comes from my Yubikey, which I unlock with a password. That means that I only need to remember one password, and it feels a lot more secure than your pattern based on url or brand.
-
Do you trust password mangers?
i use pass and keep my database on a local git repo. it encrypts your passwords with gpg and is a really simple command line program
- Comment gérez-vous vos mots de passe ?
-
Best way to store and Encrypt passwords? Need advice on my method...
If you want portability and simplicity, there's a project called simply pass that uses standard *nix utilities (and git, I believe) to manage passwords from CLI.
What are some alternatives?
KeePassDX - Lightweight vault and password manager for Android, KeePassDX allows editing encrypted data in a single file in KeePass format and fill in the forms in a secure way.
vaultwarden - Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs
KeePass2.x - unofficial mirror of KeePass2.x source code
gopass - The slightly more awesome standard unix password manager for teams
Bitwarden - The core infrastructure backend (API, database, Docker, etc).
Strongbox - A KeePass/Password Safe Client for iOS and OS X
rofi-pass - rofi frontend for pass
MacPass - A native macOS KeePass client
Pass4Win - Windows version of Pass (http://www.passwordstore.org/)
Aegis - A free, secure and open source app for Android to manage your 2-step verification tokens.
KeeWeb - Free cross-platform password manager compatible with KeePass