March 2, 2019...our season (away) opener v COL. The league wants to have more of this.

No worries...There's a concept of a plan to change this. Notebooks full of ideas. 🙄

So basically they want to loose a bunch of season ticket revenue from half the teams. Or this is how they finally decide to move to all grass pitches in soccer-specific (enclosed) stadiums? Cause they've got a plan to pay for that?

My point is mostly that /proc namespacing and parts of /proc without any make for interesting opportunities relative to common deployment patterns. Most exploits are chained, so a list of requirements is a low hurdle long term.

One example, assuming the overly common practice of privileged container (or if CAP_SYSLOG or host dmesg_restrict=0) would be to encode a to-be-broadcast message as a subprocess comm[] in a container, then segfault, and have other container recipients simply watching dmesg.

There are a number of cross container /proc sidechannels and even high bandwidth. Couple years ago I was thinking of writing a little conms library.

I wonder if @wyden.senate.gov would sponsor legislation?

Cool cool we've got a couple of pointy ball dudes to represent the Portland Thorns FC! This will solve everything for Soccer City USA.

Maybe burn something symbolic this evening?

So I went back and reminded myself (I really am not invested in the details versus confident I will never see that promise fulfilled). But I was in fact shorted pay across three work weeks / two pay periods / two months. “Trust me” HR said in the conversation I recorded.

Still short a week of promised backpay undelivered from the time period between getting fired and then getting unfired, and also months of paid for but not received health insurance benefits. But who’s counting?

Who will coach for Portland?