147 posts · Last used 4d
@karlauerbach@sfba.social @gemelen@mammut.moe
Karl, I've been evangelizing Ente Auth for a little more than two years now. It remains the ONLY fully cross-platform syncing FOSS solution available.
Mobile versions were available more than a year prior, but that didn't satisfy basic cross platform requirements. Back then there was Twilio (Authy), a proprietary solution that announced the sunset of their desktop version soon after the release of Authy desktop, and you could actually migrate your database by exporting it, interestingly enough.
Not surprisingly, they soon pushed and "update" to the desktop version which cripplewared it -presumably in anticipation of Ente Auth mass migrations.
There was a report of a flakey sync between KeepassDX and KeepassSX some time ago, yet I've never experienced issues.
Having said that, you should know that NextCloud itself reports issues with .kdbx syncing if you are stupid enough to install from the Google playstore, other sources like the git repo or F-Droid are not intentionally crippled in this way, by design, and virtue of their contract with Google.
I usually don't mention using password managers together with #MFA authenticators out of an abundance of concern for being flamed by fellow security professionals, but felt it prudent to mention here; the fact is that people will do so anyway because it's convenient.
I do separate, as a best practice, the use of my passwords and my only authenticator, Ente Auth, yet keep backup copies of my #TOTP MFA keys in a .kdbx file (in the comments - not active). I believe that's advisable to keep them in a separate vault and avoids the issue of not being able to migrate (i.e., Twillio's Authy lockdown cripple).
Sure, one could break and reinitialize their MFA on each of their myriad accounts but that's indeed a Major Pain (that's a TV pun).
So for me, I'm a staunch supporter of Pass/OpenKeyChain (sync via Git) & #Ente_Auth on all of my platforms: Android, FreeBSD, Linux (I no longer use Windows) - Sync via my self-hosted Ente Auth server; and a .kdbx client appropriate for my OS, syncing that via #NextCloud. You can use #Peergoss if you prefer.
For everyone else, I usually recommend they go with a combination of Ente Auth and [VaultWarden}(https://vaultwarden.com)
That keeps everything absolutely self-hosted and 💯% #FOSS.
If you're not a stickler for self-hosting those very same solutions are still available to you, except that for #VaultWarden you need to go [HERE](https ://VaultWarden.org).
I don't do Apple, but I am aware of .kdbx clients for that particular manufacturers products and the iPhone was, I believe, the first platform that Ente Auth was released for.
Beyond that I just urge everyone to stick with 100% FOSS solutions whenever feasible (i.e., Use VaultWarden instead of BitWarden) and make sure to contribute whatever they feel is fair to the developer teams that make all of this possible.
I hope that helps!
#tallship #Privacy #fdroid #kdbx #opensource #selfhosting
⛵
Mal eine Frage an die Nextcloud Bubble. Ich war so naiv meinen Nextcloud-Sync Ordner auf eine andere Festplatte zu legen.
Beim Großteil der Dateien funktioniert das auch. Bei einem Teil aber nicht. Unerwarteter Fehler, Sync nicht möglich.
Sogar wenn ich einen leeren Ordner erstelle und es komplett runterladen lasse.
Neu installieren und Konto komplett neu verbinden habe ich schon versucht.
This pattern repeats across every app, every platform, and the Android operating system itself. The consistent push from podcast apps, Google (Android) and the Linux desktop ecosystem is toward public certificate authorities and away from privately managed infrastructure. The people who suffer is anyone who wants to run their own server without exposing it to the internet.
Adding a certificate to Ubuntu's system trust store is straightforward and works immediately for natively installed applications. Flatpak (increasingly pushed as the Linux desktop standard) is a different problem entirely. Flatpak isolates apps from the host system, and the mechanism that's supposed to bridge host certificates into that sandbox is broken.
For several versions, Android has had a deliberate policy to hamper users to install their own certificates. It's a pain. App developers can opt in to trusting user-installed certificates with a one-line configuration change. Most haven't. AntennaPod hasn't.
None of this is technically insurmountable. But the cumulative friction across every layer... The apps, the OS, the desktop packaging format, the server appliance all pushes in the same direction: Self-hosting with your own certificates is made difficult everywhere, simultaneously, by parties who agree on the plausible-sounding security justification:
"The only safe option is to have a publicly exposed server with a CA-signed certificate". Like that's safer than accessing a server with a manually verified certificate through a closed VPN mesh network.
#selfhosted #selfhosting #self-hosted #self-hosting #antennapod #flatpak #gpodder #nextcloud #nextcloudpi
