Somewhere along the way, tech stopped asking questions like that, and now, people are hostile to the suggestion that the question should be asked.
15,237 karma · joined September 5, 2012
Somewhere along the way, tech stopped asking questions like that, and now, people are hostile to the suggestion that the question should be asked.
For decades, eery tech boom cycle is filled with people who don't understand the mythical man month, or that LOC is not a productivity metric. The AI boom is no exception. AI has not invalidated this.
It's bad enough to wrongfully send someone to prison, but to keep fighting for wrongful imprisonment when it's shown they made a mistake is downright evil.
> just trying to execute the command within the child container's filesystem
There is no such thing as changing your root filesystem or your uid from an an unprivileged process. There is no "just do it in user mode" either.
So they must have a root process somewhere doing it for you.
I just started googling, apparently for podman the setuid root binary is newuidmap
Or a setuid binary
A lot of the more important syscalls involved do require root.
But you know your audience better than ChatGPT does. Whether people react better, worse, or indifferently to the India angle will depend on the biases of the recipient.
Sounds like waitpid(2) is dangerous!
I start by saying this is about the tech behind the S in HTTPS. I say that the main point of this is that when you talk to foo.com, it has to prove that the people behind foo.com are on the other end, so it's safe to send them your encrypted password or whatever.
Then I say a bit about how the system works by having a small number of trustworthy companies vouch for other people's servers. This doesn't need too much technical detail to get the point across.
Then I say one of those "trustworthy" companies put an encryption key of 4, where it's supposed to be a long number that's hard to crack. This makes the verification easy to forge.
Then I say that everybody who runs a server needs to remove this company's bad key, and Windows or Mac or your phone needs updates too. And that your web browser probably already quietly removed it, which removes a lot of the risk.
I feel like when I explain it this way people get it.
It appears to me they do, and that is why everybody is saying to patch your python, go, and node infrastructure separately from /etc/ssl.
> which on all platforms has already had this certificate revoked from it.
I know of two systems which this doesn't seem to be the case as of yesterday.
1. I manually edited cert.pm on OpenBSD. I don't see the OpenBSD errata yet.
2. As of yesterday Mac safari was still vulnerable when I tried.
* It's absurd that Python, Go, or Node need their own certificate stores that need separate updates. (Probably OK for browsers because they seem very on top of updating them without user intervention.)
* This issue is especially bad when you consider deployment through containers, docker, etc. More parallel copies of vulnerable certificate stores. With docker volumes you could mount the host's certificates into the containers and get "update once" behavior but I doubt people are doing this.
* It wouldn't be too hard to implement CRLs against the OpenSSL certs as a script that runs from cron. I might end up doing this.
sudo certctl untrust /usr/share/certs/trusted/emSign_ECC_Root_CA_-_G3.pem
And on OpenBSD by editing /etc/ssl/cert.pem, removing everything starting from the line: === /C=IN/OU=emSign PKI/O=eMudhra Technologies Limited/CN=emSign ECC Root CA - G3
Up to but not including this line: === /C=IN/OU=emSign PKI/O=eMudhra Technologies Limited/CN=emSign Root CA - G1On the other hand my life experience is often that people who accuse others of doing activities in secret, and being dishonest about it, that is often, but I will give you not always, indicative of where their own head is at.
It's not just overused — it's a cliche now.