334
Bitwarden Makes Change To Address Recent Open-Source Concerns (www.phoronix.com)
submitted 2 years ago by to c/technology@lemmy.world
76 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 1 point 2 years ago (1 child)

Trusting one FOSS client good. Trusting different FOSS client bad. Logic where?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years ago (1 child)

    That different FOSS client stores your data on their company's server. It's an important factor, IMO.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years ago (1 child)

    Dude, how is bitwarden hosting your own, locally encrypted (in FOSS client) password database any different than using keypass and syncing it however you want?

    I don't even use Bitwarden myself, I'm using keepass too, but this attitude is ... weird?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years ago* (1 child)

    I find risk slightly bigger when you encrypt your private data with the product of the company and store that encrypted data on servers of the same company.

    Why: because if they have some backdoor now or plans to introduce it in future, they have all the time in the world to apply that backdoor to your data. Without you knowing it.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 0 points 2 years ago (1 child)

    Bitwarden client is FOSS same as Keepass, though. Why aren't you afraid of Keepass having backdoor by "insert whatever big corporation sponsoring FOSS" giving said companies free access to your passwords you happily store in their clouds?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •