• e8d79@discuss.tchncs.deOP
    link
    fedilink
    English
    arrow-up
    6
    ·
    3 months ago

    There is an unofficial mono port available but it looks like ass and, since it also can’t do autofill in my browser, it has no benefits over GNOME Secrets.

    • Forester@pawb.social
      link
      fedilink
      English
      arrow-up
      7
      ·
      edit-2
      3 months ago

      I’d never trust the browser to have direct access ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯ i copy paste

      • rook@awful.systems
        link
        fedilink
        English
        arrow-up
        5
        ·
        3 months ago

        That’s a funny thing to say. The communication channel between the browser and whatever external password store can be made as restricted as you like… keepassxc and its browser api let you restrict which credentials are offered to the browser, and can let you manually OK each request, for example. It doesn’t need unrestricted read access.

        The bitwarden browser plugins are a bit more dubious though, because they communicate with a remote password store with more limited controls, and their enthusiasm for trying to store passkeys and totp hashes is definitely worth avoiding.

    • cecilkorik@piefed.ca
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 days ago

      I’m running the Keepass2 packaged with Debian, which uses the mono port, and while I agree with your assessment that it looks like ass, it works perfectly, runs plugins, and integrates with the Kee addon in Firefox/Librewolf no problem.

      Obviously I wish there was an official Linux version and I almost migrated to KeepassXC, but can’t live without the built-in Sync function in Keepass original. While it was a bit of a beast to get set up initially, with some permission problems and the awkward process of installing plugins, I’ve now been using the mono version for over a year with no issues and can recommend it, for functionality at least.