• adr1an@programming.dev
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    Not to flame on anyone, and without reading the details on the specific CVE. But, to share as an advice: this reason is why I prefer keepass + syncthing for my needs. Security for a full blown web app is not trivial and has a bigger “attack surface” than a kdbx file moving p2p through my devices via syncthing.

    • kolorafa@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      1 month ago

      Explain how can you use KeePass+Syncthing with 10-50 people (possibly different groups for different passwords) having different sets of access level while maintaining sane ease of use?

      The passwords are encrypted in the first place so the security for them is only on the client side.

      • khorak@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 month ago

        I do not have to share passwords with 10-50 people and neither did the op imply this. I am having trouble figuring out the reasoning behind your message. Why would this be a normal use case?

  • keyez@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    Interesting the CVEs don’t have information yet and didn’t appear to affect bitwarden and it’s containers. Haven’t seen a security release from them since around March.