With a lot of help from @kinetix, I finally got #Vaultwarden up and running. It’s a bit clumsy in areas and some aspects seem over-complicated, but once you get used to it all, it works quite nicely. The only issues I’ve found so far are creating accounts/changing account passwords silently fail (the submission button does nothing at all) if you leave the option to check your chosen password against the HIBP breach checker selected but you don’t subscribe/pay for a HIBP key. Also, disabling certain features doesn’t hide those features/forms from being available; you can complete a relevant form and it will only fail upon submission, with an error telling you that the feature isn’t available. I’ve found this specifically when the “sends” feature and open registrations are disabled; #Vaultwarden will still allow you to go through the motions. Organisation setup is useful for a small business or your family, with granular permissions. Overall, I’m very pleased with #Vaultwarden so thanks to @neil and @feld for suggesting it and to @kinetix again for getting it up and running for me!
#BitRitter now has support to open links from the detail page (or copy them). Also, Custom fields are shown on the detail page.
To smooth the overall experience, i got a basic search filter working, so you don't have to scroll to your desired #VaultWarden entry.
Same API, same features, same UI, and support for other DBs than MSSQL.
One single stand-alone application vs. Bitwarden’s 10 Docker containers. 70MB of RAM vs. 2GB. 3MB of db storage vs. 300MB.
Why was a password manager supposed to take so many resources in the first place? Just because it runs on a Microsoft-only stack and on .NET’s inefficient VM? Just because somebody thought that it was a good idea to separate everything into different containers (even icons and 2fa are modeled as separate services in Bitwarden)?
It reminds me of my recent migration from Mastodon to Akkoma. I got more features, 5GB of RAM freed up and 300GB of storage freed up almost overnight.
Writing and running inefficient software that pointlessly consumes all the resources available on a machine should be a crime in a world with limited resources.
It makes me think of how much shitty bloated software like @bitwarden, probably based on awfully inefficient languages and frameworks like Java, Ruby on Rails and .NET, is running out there, pointlessly sucking up resources for doing simple jobs that could easily be done with 99% less resources.
Today’s developers, spoiled by IDEs, powerful machines, docker-compose and shortsighted “just throw more RAM at the problem” approaches, have forgotten how to write efficient software. Time for them to learn how to write good efficient software again. Software doesn’t eat the world. Only shitty software built on shitty framework does.
I could self-host the family's password manager… probably don't want to do it on the home NAS. Maybe a tiny cloud server? I think it just needs Docker access, a port, and a little storage.
Making progress with #BitRitter. Slow, but steady.
Today i implemented a password input to unlock the #BitWarden / #VaultWarden vault, so we can soon remove a part of the credentials.toml (which was just a workaround for faster testing) and make the app safer. #Relm4 feels nicer the more i get to work with it.
Sadly my ARM CI did not work as nicely as the x86, so i can't package for my phone easily.
My first (very incomplete and WIP) iteration of my #MobileLinux#BitWarden client. It ia usually not ready for others to use, but i need to publish it to stay motivated.
Works with #VaultWarden aswell. You have to build it fron source though, for the time being.
Installed #Vaultwarden. Will have to tinker with this later to see if it's worth moving my vault to a self-hosted instance instead of directly with #Bitwarden
Come già annunciato da diversi mesi i servizi #bitwarden per la gestione delle password ed #etherpad per la #scritturacollaborativa sono migrati alle 24 del 24/1/24 e sono ora disponibili qua:
:bitwarden: https://vaultwarden.devol.it
è sostanzialmente lo stesso software open source compatibile al 100% con bitwarden, il progetto è stato rinominato dallo sviluppatore.
hello :mastodon:
je cherche à mettre en place de l'authentification à plusieurs facteurs pour les services ou je suis inscrit mais je me demande ce qui est le mieux.
Je veux pouvoir utiliser mon téléphone ou un autre service car si je le casse ou je le perds bah plus d'authentification multiple.
Je pourrais le mettre sur mon #yunohost mais pareil, si on serveur crash, ma maison brûle ou on me vole, même soucis.
Idem pour #vaultwarden qui est sur le Yunohost.
@zaherg Nope, not leaning my 2fa codes to a closed source product 😆
In all seriousness, I already use @bitwarden + #vaultwarden open source alternative backend self-hosted, so even though that may be a good alternative, I don't need to overcomplicate my flow.
Farewall Lastpass (premium), it was a rocky ride. I was 2 years late to delete my dormant account anyways.
I had migrated to self-hosted and dockerized Vaultwarden ( Open source alternative @bitwarden backend ) last year, along with official clients. Loving the overall experience so far!
Vaultwarden kannst du sehr einfach selbst mit Docker hosten, oder einen Freund mit Kenntnissen bitten, das für dich zu tun.
Bitearden ist dann als App auf Android, Linix Windows oder Mac verfügbar und auch als Browserplugin.
Und für "Unterwegs" kannst du auf vaultwarden sogar per Weboberfläche zugreifen... wenn es wirklich sein muss, auf unbekannten Rechnern so etwas sensibles aufzurufen und einzutippen...
Primary storage ist via #bitwarden with a local #vaultwarden installation (both needs to be version 23.10 at least)
Secondary storage is a #yubikey 5 NFC which I carry with me. This one alllows me to use the passkey on my iPhone (iPad not tested yet)
Tertiary storage is another (cheaper) Yubikey which is deposited in a safe at home
Both Yubikeys are protected by a PIN which my wife knows. That way I canot lose access to my account and have taken precautions in case I become incapacitated.
But this setup requires quite some time for each web site to switch to passkeys. That's why I am so angry with companies like Paypal who make it practically unusable.