Login
You're viewing the functional.cafe public feed.
  • Sep 1, 2026, 8:39 AM

    Okay so KeepassXC is doing slop (and I haven't checked their code quality lately), pass uses GPG (which is a Kill It With Fire feature for me and Should Be For You Too) and 1Password is supporting the fascists. Is there any password manager left that can be recommended without holding one's nose? :blobcatnotlikethis:

    💬 1🔄 3⭐ 1

Replies

  • 💬 0🔄 0⭐ 0
  • Sep 1, 2026, 8:47 AM

    @natty not a password manager. But pass but using age would … probably be okay? Lacking a lot of infrastructure so still not a good recommendation for anybody but weird nerds but hey

    💬 0🔄 0⭐ 1
  • Sep 1, 2026, 9:04 AM

    @dequbed @natty At this point I'd mostly recommend pass and considering the GPG layer as though it wasn't present if pass fulfills your use-case (I'm not sure if one can't simply disable it?).

    Some manner of LUKS loopback device file or preferably (Linux slop makes LUKS questionable to use) other userspace-provided better encryption should be used.

    💬 1🔄 0⭐ 0
  • Sep 1, 2026, 9:06 AM

    @lispi314 @natty No. GPG is a Kill It With Fire level decision. I will not use software tainted by it if I have alternatives and I will certainly not recommend it (and I *do* have alternatives)

    💬 0🔄 0⭐ 0
  • Sep 1, 2026, 9:08 AM
    @dequbed @natty > (and I *do* have alternatives)

    I was personally disappointed by most alternatives I found, in their password management capacity and reasonable auditability of their code.
    💬 1🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Sep 1, 2026, 9:12 AM
    @dequbed @natty In terms of active malice that would initiate new nonsense, I have not as I consider it clear from that especially in older versions (it has been scrutinized enough better than me would have found it).

    (Of course any codebase that is slopped or shows signs of "agent" use doesn't need review, it is deleted. Somehow a few candidates I initially found qualified under this.)

    In terms of cryptographic competence? What I've heard is damning and I consider it probably useless on that level.

    So in this application I would consider it a bizarre binary encoding with no meaningful security property. At least it doesn't randomly corrupt itself so I can mostly ignore it.
    💬 1🔄 0⭐ 0
  • Sep 1, 2026, 9:17 AM

    @lispi314 @natty now read that back and tell me why pass is a workable alternative compared to e.g. KeepassXC. That one at least comes with cryptographic protection of your key database.

    💬 0🔄 0⭐ 0
  • Sep 1, 2026, 9:20 AM
    @dequbed @natty KeepassXC is being actively slopped and I don't feel like spending the effort of forking it or further extending it.

    Scripting extensions for pass is much easier and I can more easily tie it with other tooling to cover new use-cases.

    (KeepassXC is C++ and I just really don't feel like it.)

    Encryption can be managed separately, and since I mostly use Qubes it's not like anything has access to that network-less qube's filesystem or memory at any point.
    💬 2🔄 0⭐ 0
  • Sep 1, 2026, 9:23 AM

    @lispi314 @natty “Sure, just write your own extensions/features” also does not make for a good recommendation for anything but weird nerds. I'm not denying that pass words for *you* but it solves none of the problems I have or that I consider important in a general recommendation for password managers (and that *is* what this thread is about)

    💬 0🔄 0⭐ 0
  • Sep 1, 2026, 9:28 AM
    @dequbed @natty Fair.

    Honestly I don't have a better user-friendly option than "just keep using a pre-slop keepassxc version" which is probably fine unless some corruption bug was found.
    💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • 💬 0🔄 0⭐ 0
  • Sep 1, 2026, 11:00 AM

    @dequbed I'd stay within the keepass file format universe, I haven't checked yet but I'd strongly hope there'd be at least one unslopped KeyPass client out there

    💬 0🔄 0⭐ 0