this post was submitted on 20 Oct 2024
370 points (95.1% liked)

Selfhosted

40133 readers
545 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Bitwarden introduced a non-free dependency to their clients. The Bitwarden CTO tried to frame this as a bug but his explanation does not really make it any less concerning.

Perhaps it is time for alternative Bitwarden-compatible clients. An open source client that's not based on Electron would be nice. Or move to something else entirely? Are there any other client-server open source password managers?

you are viewing a single comment's thread
view the rest of the comments
[–] 4shtonButcher@discuss.tchncs.de 113 points 3 weeks ago (3 children)

Can’t we ever have software that just keeps working? Password managers are like the new RSS readers.

  1. search around for a good one
  2. find a nice one and start using it
  3. they add stuff you didn’t want and slowly make it worse
  4. they’re bought up/ abandoned/ otherwise become unviable

Back to 1)

[–] brayd@discuss.tchncs.de 40 points 3 weeks ago (1 children)
[–] jasep@lemmy.world 73 points 3 weeks ago (3 children)

The downside to Keepass is it is not self hosted, as in it's designed to run locally per device. Yes, you can put the database file on a network and have multiple clients from different operating systems access the database, but you will end up with collisions and database issues. Ask me how I know.

Running cross platform Keepass (and it's various forks) is absolutely doable, but it is not as seemless as BitWarden. I'm running self hosted VaultWarden and I'm hoping to run it for a long time as it's much easier than Keepass.

[–] thayerw@lemmy.ca 20 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

For what it's worth, I only ever had sync issues when sharing a database between devices with transient connectivity. Once I added an always-on instance of Syncthing into the mix, collisions were a thing of the past.

We've been using KeePass trouble-free for many years now, sharing a single database across more than 6 devices, with frequent use and modification.

[–] clmbmb@lemmy.dbzer0.com 42 points 3 weeks ago (3 children)

Syncthing just announced they won't develop their Android app anymore. 🫤

[–] thayerw@lemmy.ca 22 points 3 weeks ago

Noooo! Ugh, that's so disheartening to hear but I can't fault imsodin for his reasons. I sincerely hope that someone steps up to the plate, even if only for the F-Droid releases.

For anyone else interested, the discussion is taking place here:

https://forum.syncthing.net/t/discontinuing-syncthing-android/23002/7

[–] gazby@lemmy.dbzer0.com 13 points 3 weeks ago* (last edited 3 weeks ago)

Ah shit, I hadn't heard that. Another one bites the dust because of Google's Play Store insanity. Maybe SyncThing-Fork will continue? 🤞

Source: https://forum.syncthing.net/t/discontinuing-syncthing-android/23002

Edit: Aaand like 10 posts down in my feed https://lemmy.world/post/21070831 lol 😭

[–] hunkyburrito@lemm.ee 2 points 3 weeks ago* (last edited 3 weeks ago)

While the official syncthing-android is no longer being updated, syncthing-fork is still going strong

[–] gazby@lemmy.dbzer0.com 6 points 3 weeks ago

KeePassXC here, ÷1 for the exact same issue with the exact same solution (ST with an always-on "server") 👍

[–] PureTryOut@lemmy.kde.social 16 points 3 weeks ago (1 children)

Eh, I have used KeepassXC over multiple machines using NextCloud to sync it for years now and have never had any conflict.

[–] somenonewho@feddit.org 3 points 3 weeks ago

This. I have been running it the same way for some time now. Even if you change something on one machine and something else on another nextcloud will just happily inform you of the conflict and then you can open both databases and cherry pick. Never had corruption issues.

[–] brayd@discuss.tchncs.de 2 points 1 week ago

Yes, that's a fair point

[–] narc0tic_bird@lemm.ee 14 points 3 weeks ago

Bitwarden keeps working just fine.

[–] catloaf@lemm.ee 1 points 3 weeks ago (1 children)

Sure, you're welcome to keep using the version you like, or to write or maintain one on your own. Or pay someone for their labor to do it for you.

But if you use something made out of someone's good will, don't rely on it for anything critical.

[–] gdog05@lemmy.world 6 points 3 weeks ago

Money isn't necessarily a factor. I've paid for many services that have made business or operating changes to the point of needing to separate and then there's WinZip on the other side of things.