An idiosyncrasy I have about TIL posts is that I think they should focus on what you were able to got done/progress with.
TIL posts that truly have been learned that day, or recently, often contain subtle errors explicitly or implicitly. Which isn’t a problem in and of itself but in a when such posts get used as the basis of someone else’s TIL post these errors often get compounded.
As an example I find almost any TIL style post about a text editor to be like this. To give a contrast Chris Siebenmann‘s blog [1] does give focus to what was done. Also the author is reasonably good about making corrections in edits or follow up posts.
The banishing of the Bounty is one of the few purely good pieces of news we've had! I mean I'll cave a few days after Christmas and eat them but I'm not happy about it.
Naive question what are the non-nefarious requirements of being able to do this? I get that people have used it to work around things (for good and ill) but what’s the vanilla answer?
One of my favourite Futurama gags is the opening caption of S07E25 - "Stench and Stenchibility" which reads “Not the Episode with the Dead Dog” in reference to S04E07 - "Jurassic Bark". If you’ve not seen the latter I highly recommend it, the former quote does not prepare you for the emotional gut punch.
I came across tylr the other week which looks very interesting. Probably easiest to watch this video[1] first then play with the demo and read the paper [2][3].
I'm just going to dump some other links to pledge just for others that are interested. Here's some presentations on attempts at natively implementing pledge in Linux (YouTube's auto-translate does a decent job) [1][2].
The topic of a pledged process starting other processes un-pledged often comes up (and already has done in the comments here). I'd recommend checking out this section of Theo de Raadt's presentation that explains why this is [3].
As mentioned in the article the nice thing of pledge on OpenBSD is the integration of the pledge interface with the reality of underlying system. So as one example a program can pledge only dns and say not have filesystem access, but really under the covers it can read /etc/resolv.conf.