It uses bubblewrap for sandboxing under the hood, right?
It uses bubblewrap for sandboxing under the hood, right?
I’m too lazy… Yeah I am pretty nerdy, but I still don’t want to spend that much time caring about my selfhosting setup and building a homelab. But I’m glad it works for you, and I’m glad ente created their authenticator in the first place. I would have never expected it from them, since they only used to make ente photos, but there we go, they casually just created the best FOSS auth app.
I know, but I use the cloud hosted ente auth backup method on purpose, because I don’t trust myself with selfhosting and I’m too scared to accidentally rm -rf
my server and lose my 2FA seeds. That’s also why I don’t selfhost bitwarden, even though Vaultwarden is pretty great, and even offers Bitwarden Premium features for free (and I love it cause it’s written in Rust lol)
Is self hosting even worth it for auth? I self-host ente Photos myself, because that way I don’t need to pay for a subscription, but auth is free anyway, and the backups are entirely e2ee, right?
Can CLI applications inside Termux interact with the Android clipboard?
We have USB/NFC hardware security tokens, as well as OS-integrated passkeys
albeit it being only source available
Isn’t that exactly why we need to leave the official Bitwarden client for something else?
Absolutely
Either use secure, encrypted VoIP calls (e.g. over Signal or another secure messenger with an end-to-end encrypted call feature)
Or you use a secure messenger that only runs on smartphones and doesn’t have a desktop client
Nope. Since the entire database is contained in a single file, it can’t sync multiple edits properly, leading to sync conflicts. Because KeePass was built around local database files, whereas Bitwarden uses actual synced databases, where individual updates can be uploaded, instead of causing conflicts or overwriting the entire db.
It definitely has a nicer design and blends in well with the rest of the system (at least on Android)
Bitwarden can’t be compared to KeePassXC. Bitwarden is fundamentally built around a sync server, whereas KeePass is meant to exclusively operate locally. These are two very different fundamental concepts for, you know, how to actually store and access your passwords.
LibreWolf (which doesn’t store any cookies or other website data by default, unless you allow it) + I still don’t care about cookies or Consent-O-Matic
Hell yeah
Use LibreX or a fork called LibreY, it’s a JS-free proxy for Google search
There’s a list of instances at https://librey.org/instances.php
Something similar exists for DuckDuckGo btw, it’s called 4get
Or you can just use SearXNG, a meta search engine that aggregates results from multiple sources
Removed by mod