Is there an open source no-AI password manager out there?

Trying to bail on BitWarden… KeePassXC (with SyncThing) seems to come up as the most recommended, but they’ve been using copilot. Seems like they might still have the strongest anti-ai stance of the available options though, despite that.
#PasswordManager #NOAI @fuck_ai

  • Lucy :3@feddit.org
    link
    fedilink
    arrow-up
    16
    ·
    12 days ago

    Then just the the normal/official KeePass client. Old as hell but probably therefore also AI free.

  • JangleJack@lemmy.world
    link
    fedilink
    arrow-up
    11
    ·
    12 days ago

    I like KeePassXC and SyncThing for my own use. I am not sure that I am ready to apply a no-llm purity test if a dev is using a model appropriately. If the code becomes obfuscated somehow, that would be another matter. In the longer term I hope FOSS devs do not come to rely on paid cloud models or favor code quantity over quality.

  • nublug@piefed.blahaj.zone
    link
    fedilink
    English
    arrow-up
    8
    ·
    12 days ago

    chipass is a strict no-ai fork of the last keypassxc version without ai code. it’s got a banner warning that’s it’s in dev and may likely cause corruption so make regular backups of your db, but i’ve been using it for a week or so with no issues so far.

    as for android, i’m using keepass2android as it’s got a fancy cloud saving feature where i can keep the db saved in my nextcloud and easily sync the db on my desktop as well.

  • yeehaw@lemmy.ca
    link
    fedilink
    arrow-up
    7
    ·
    12 days ago

    Been using keepassxc for well over a decade and syncing with nextcloud, but yes syncthing works too. Only once did my database go corrupt, but I have zfs snapshot and nextcloud has versioning too so it was no big deal.

  • NO FUTURE@thicc.horse
    link
    fedilink
    arrow-up
    6
    ·
    12 days ago

    @MxRemy @fuck_ai I use and love “pass”, a command line local password manager for linux. Instead of syncthing I use git to manage versioning and synchronization.
    I know that’s a super limited use case, but there are GUIs and TUIs available for pass, and other manager tools may be built on top of it, I’m not sure

  • hexagonwin@lemmy.today
    link
    fedilink
    arrow-up
    2
    ·
    12 days ago

    keepassxc is fine… i’m aware they’re testing LLMs in the development process but last I checked it was sane enough and quite understandable

    • Remy Rose@todon.euOP
      link
      fedilink
      arrow-up
      1
      ·
      12 days ago

      @vala whoaa what!! Lemme see if I understand this right… It’s less of a password manager and more of a deterministic password generator? As in, it’ll always spit out the same resulting password given the correct input passphrase + domain of the site being logged into? So you just essentially generate it again instead of ever storing it.

      I’m so amazed and curious about this approach, what are the pros and cons? Obviously there’s still the risk of someone learning your passphrase, but there’s no hackable database of passwords. Do you get a different output from different variations of the same URL, like including a “/” at the end? What does saving the bookmark actually do, like pre-fill the URL field? Given that autofilling is supposed to be more secure than copy/pasting, is there some way to make this do that?

      Sorry for the barrage but I’m very tempted by this one, it’s neat!

      • vala@lemmy.dbzer0.com
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        12 days ago

        Yeah that’s more or less how it works. You generate it deterministically every time.

        what are the pros and cons?

        Not really sure of the cons aside from the fact that you get significant “vendor”/algo lock-in. You need the exact same algo this app uses to get your password back out (good thing it’s GPL).

        Do you get a different output from different variations of the same URL, like including a “/”.

        Yeah an extra slash at the end means a whole new password. The “name” is not really a “URL” per se. It can be any string.

        So for example “lemmy.dbzer0.com”, “vala@lemmy.dbzer0.com”, and “lemmy.dbzer0.com 2” are valid site names and will give different passwords.

        That being said I could see omitting some special trailing chars, protocol strings etc.

        What does saving the bookmark actually do, like pre-fill the URL field?

        Basically every parameter of the password generator is codified into the URL. So bookmarking a URL allows you to load a page with prefilled data like:

        • Special chars
        • Length
        • Revision number
        • Algorithm
        • etc

        These parameters are all required to be the same each time you need to generate the password. So it can help you avoid filling these forms each time + act as a reminder of what you used.

        Given that autofilling is supposed to be more secure than copy/pasting, is there some way to make this do that?

        It will auto-fill your master passphrase but if you mean auto-filling your credentials into sites, it would need to be made into a browser plugin to do that.

  • altphoto@lemmy.today
    link
    fedilink
    arrow-up
    1
    ·
    12 days ago

    Hmmm I’m using vaultwarden. Its a fork of bitwarden that is opensource. My problem with it is that you have to use the bitwarden app. But it is opensource and as the web corrected me last week when bitwarden’s CEO went Nazi, it is completely unrelated to bitwarden. Except that at least one of bitwarden’s engineers who is not a Nazi but works for one is allowed to work on vaultwarden by that Nazi CEO.

    Maybe not a Nazi, but the new CEO is a private equity type that tend to enshitify things. So he started by removing the 'always free" and changing the company’s stance on supporting equality to nothing…so Nazi.