Your friendly neighbourhood sh.it.head
A Reddit refugee after 8 years of Reddit-ing
This is perhaps overkill, but you can also encrypt the contents of your online cloud storage with CryFS / Cryptomater. This is particularly useful if you wish to store sensitive documents (healthcare, finances etc) in a cloud environment in case of catastrophic destruction of property (destroying computers / on site backups of data).
In this case you can also backup your keepass file in this encrypted virtual storage medium, on top of the prexisting encryption of the database itself.
My personal choice right now is KeePassXC (PC) / KeePassDX (Android) + Syncthing And Aegis (Android) for 2FA codes, with a yubikey for services that support FIDO keys.
Overall I like this setup because it’s decentralized and does not rely on a third party server structure. The only “weak” point would be the Syncthing relay servers or the Tailscale VPN that I use, but this goes back to ensuring encryption of the database is adequate with a long password, and using an open source synchronization protocol that ideally has been vetted by a trusted third party (or yourself if you’re capable)
I used to use Bitwarden, and I highly recommend it. I really appreciated it’s ability to integrate with email aliasing solutions to generate new aliases from within the bitwarden UI itself. However, my main reasons for switching were the following
The only additional advice I have for both recommendations is that I do not think it advisable to add Totp 2fa information to your password manager even if it supports it. I feel like this should be separate, on a single device, and backed up in ~2 locations (one preferably off site). This is really to avoid problems if a device is compromised and if your password manager is compromised, but this is definitely in the more unlikely category I feel.
My only major issues with keepass are the potential for sync conflicts and the some feature differences between platforms. A centralized server config like vault/bitwarden prevents the sync conflict issues, at the cost of having one point of failure. The feature differences problem isn’t too great, but autotype doesn’t work on Linux if you install with flatpak, and you can’t prevent screen capture of the app on Linux (only on Android and Windows from my understanding)
Edit: I also tried gopass, it’s really fun to have an entire CLI based password manager, but frankly the state of mobile companion apps are appalling. The Android option only is good if you use a dev version, and the iOS one I thought was just ok. I also dislike the metadata leaking that is inherent to the format, and that PGP is the main form of encryption for the time being (some clients were looking at using AGE at some point). Overall it’s a cool but flawed concept, and I feel my other two recommendations are superior.
I think it’s important to see these types of efforts, while I’ll never go out and buy a MacBook the effort isn’t wasted since it gives current users more freedom and future people buying used laptops more options for Linux compatible hardware.
Without a project like this, that hardware will end up being e-waste a lot sooner than it should be, when Apple drops support. At least to me I see an ethical and moral imperative for projects like this, but I also understand people’s grievances with Apple.
I might make the plunge soon as my desktop is just slightly too old—but, at the same time, I need Windows for a few things for work so it’s a little frustrating 🫠
Gaming wise I’m completely able to use Linux, but I also don’t really play competitive games with anti-cheat so it is not exactly surprising.
I think you summed up my thoughts on the matter much better than I could have. In particular, the “digital” / “corporate” right to be forgotten is distinct and much more specific in its scope than a broader right, and is a rather important consumer protection in my opinion.
Do you have a separate computer that you can use to do a “test run” of using Linux? If not, I would at least play around with Linux in a virtual machine before committing to the bit (and I say this as someone who has been using Linux laptop / Windows desktop for 6-7 ish years now)
You have a few options on what you can do to limit your child’s usage of a device.
NextDNS has some interesting features for parental controls, as well as some options to try and prevent bypassing it (i have yet to try it though). On iOS it can be installed as a device profile and you can prevent them from being uninstalled, I’m not sure how to go about this on android but I’m sure there’s a way of limiting the child’s access to changing the settings.
Otherwise the built in parental control features on Android and iOS seem to be very useful as well, since you can limit what your child can install, set screen time limits, etc. I am pretty sure you’d want a more recent version of Android however to get all of the features here which may not be possible depending on the budget.
If you just want the ability to call / text then perhaps a dumb phone is a good first step? But a smart phone may be more useful if they’re older.
For iOS devices the most up to date client is “Strongbox”. I don’t think it is FOSS, but is compliant with the standard. It’s sadly a freemium app, but is quite well made in my testing. It cannot sync with syncthing, but does support several cloud services, its own service (which uses iCloud), and local file transfer over LAN. They also have a version of the app with all network connectivity removed for security (if you prefer)