• Routhinator@startrek.websiteEnglish
      0·
      15 days ago

      I’ve always loved Keepass, however I moved away from it in 2012 as it and any file based vault has brute forcing issues. You need to track every copy of it that has been made and if any copy falls out of your hands, like if you lose a device, you need to do a password rotation on 100% of your passwords. Since its a file, its not possible to prevent brute forcing.

  • gwen@lemmy.dbzer0.comEnglish
    0·
    15 days ago

    can we start reading the articles and not just the headlines??? it literally says it’s a packaging bug

    • 486@lemmy.worldEnglish
      0·
      15 days ago

      It is really not just a packaging bug. If you read that comment of the Bitwarden person a little further, you’ll notice that he’s talking about that proprietary “SDK” library that they are integrating with their clients. Even if they manage to not actually link it directly with the client, but rather let the client talk to that library via some protocol - it doesn’t make the situation any better. The client won’t work without their proprietary “SDK”, no matter if they remove the build-time dependency or not.

  • ayyy@sh.itjust.worksEnglish
    0·
    15 days ago

    600 upvotes and only 10 downvotes on literal fake news. I wish readers were less lazy, it’s very frustrating.

    Edit: made my statement a bit less toxic. I was mad.

  • Shape4985@lemmy.mlEnglish
    0·
    15 days ago

    I use to always recommend bitwarden to people. Now i feel like an idiot for doing so with them switching up. Ill be making the effort to move to keepassxc soon and host it myself.

  • cmrn@lemmy.worldEnglish
    0·
    15 days ago

    EDIT: The article has been updated and it was described as a “packaging bug” and not an intended change.

    How many times do I need to pack up and move to the next “best option”

    • sugar_in_your_tea@sh.itjust.worksEnglish
      0·
      15 days ago

      In this case, zero, because it’s a packaging bug, not an actual change in direction. Read the update on the article:

      Update: Bitwarden posted to X this evening to reaffirm that it’s a “packaging bug” and that “Bitwarden remains committed to the open source licensing model.”

      Next time, before jumping to conclusions, wait a day or two and see if the project says something.