Even in the US, selling to kids is illegal in most states, so the same issue applies: kid can't buy vape at store, kid goes to adult who is likely to be criminal to get them to buy for them, now kid is vulnerable to exploitation.
I recently did a deep dive on cli password management in an attempt to harden my bash scripts. (yes, I love bash, despite HN always loving to talk crap about it)
Pass is just a shell wrapper around gnupg, when you run pass some/secret/path, what actually happens is pass constructs and executes a gpg command (e.g., gpg --decrypt ~/.password-store/some/secret/path.gpg) and the output of gpg (the plaintext secret) is piped to pass's stdout.
Most people know this though. What I learned I didn't know before though was this:
Memory Zeroing: after it's used (e.g., copied to a pipe or stdout), GPG's internal memory management aims to zero out those memory regions used as soon as they are no longer needed
Memory Locking: GnuPG also uses mlock() (or equivalent OS-specific calls) to lock sensitive memory pages into RAM. This prevents the plaintext keys and decrypted data from being swapped out to disk, protecting against swap-file forensics or cold boot attacks.
I had been banging my head against bash trying to do those things manually, and ended up with the conclusion it was best to use pass/gpg with the following addendums (from my notes in my skeleton secure bash template):
1. Minimize secret lifetime: Use subshells, functions with local variables, and unset, disable bash history
2. Pipe secrets directly: Pass secrets via stdin or process substitution directly to the consuming program without intermediate variables if possible.
3. Rely on the tools: Use pass, gpg, or KMS CLIs that are themselves implemented in lower-level languages and can (and should) implement these memory protection techniques internally.
Security, including privacy, is about layers of hardening. In this case, minimization of leakage and other privacy concerns for some can still be worth the tradeoffs. For example, some apps literally refuse to work on a completely de-googled phone. (I ran one for many years with no google services). Also, the general control the user gets offers a lot more ability to harden than most android. I bricked my phone and am currently borrowing one and using stock android and there are things like facebook that are literally uninstallable... At least on lineage/graphene the user can actually control the system.
No, because it became a locked down ecosystem that is user-hostile and not user-controllable. I realized this when I observed the younger generation, who I thought would be much better than us at computing, who had not a clue how anything worked because they never had the ability, need, or desire to tinker with the underlying systems, with only rare exceptions (roms, etc).
Depends on your lifestyle and location. The only thing I use my cellphone for is text messaging and looking at wikipedia or part numbers when im not at home. It is definitely useful, but 95% of my computer work is still done on a PC.
I grew up in the mountains at about 8500 ft, but was often spending my freetime at higher elevations surrounding the village. There are lots of little things about living at high altitude people don't think about, such as cooking times and quirks, sealed containers exploding when going up, etc. My favorite has to be just how superhuman (when I was in my prime) going down to low elevation made me feel.
The biggest issue people don't talk about? Remote high alt places often become unlivable for people when they get elderly due to altitude interference in certain medical conditions, and the general distance away from hospitals.
I miss the mountains so much all the time, and hope to retire back up there.
As a linux admin, I refuse to install npm or anything that requires it as a dep. It's been bad since the start. At least some people are starting to see it.
