Just dropped another few paragraphs into PSI spec.

One day it may get there... 🥺

#Podcast recommendation: The current episode of #ACM #ByteCast is featuring Monika Henzinger, on lots of interesting topics such as differential #privacy and predictive #ML and her career path through #academia and #industry.

https://acmbytecast.podbean.com/e/monika-henzinger-episode-92/

(not yet in ACM's own archive; might change by the time you read this, see https://learning.acm.org/bytecast/archive )

OH: "Das wird WordPress fixen."

OH: "Ich steh' nicht so auf Gesetze."

If 4 is too little, try 44.

Contextual joke:
There is a dance club next to @daslabor named Cypher 44; https://cypher44.de

RE: https://fosstodon.org/@Gina/117483371670841266

Pro tip for podcasters: Don't be jerks.

RE: https://social.treehouse.systems/@grawity/117480732617892779

Essentially needs lots of rebuilds/updates, nothing special.

On that note:
So do all those Docker/container images.
And all your systems.

I saw the (implied) question come up if a single global, content-addressable (cert) store for the entire universe would help; but: bottlenecks, agreement, ...

I am thus comparing this to the neverending discussion around shared libraries.

One property of embedding and bundling is resilience through self-sovereignty. But it's also a chicken-and-egg problem.

One thing rarely mentioned around the #eMudhra whoopsie is that the whole #PKI scheme was designed to be resilient by having many CAs.

It was just a matter of time that another issue surfaced.
This is by far not the first time a CA is having a problem.

So yea, you *can* distrust, revoke, etc..

If you are running (critical) infra, please consider a Principle of Least Trust approach. I.e., only explicitly trust those few CAs that are really involved in your service(s).
Another checklist item ✅️.

The main difference between #PHP and many other programming languages iis that PHP made it on regular TV. It is kind of having its CrowdStrike moment, if you will.

https://youtu.be/ZJdNBhC7IvE?t=512

And now be kind to them. Thanks. :3

Props to Qualcomm for explaining publicly how their boot authentication mechanisms work - they have done a lot of their homework!

https://www.qualcomm.com/content/dam/qcomm-martech/dm-assets/documents/secure-boot-and-image-authentication-version_final.pdf

RE: https://bsky.brid.gy/r/https://bsky.app/profile/did:plc:x7vfp7rt4gbywara7ljm5e2s/post/3myf5dvjjcs2f

Lasst euch nicht einschüchtern von Leuten, die Angst vor einem Regenbogen 🌈 und einem Döner 🥙 haben.

RE: https://infosec.exchange/@cheri_alliance/117479646735238777

CHERI on RISC-V will be neat...

https://github.com/riscv/riscv-cheri

RE: https://nrw.social/@Colognerin/117479591627358718

woop ✨🏳️‍🌈🏳️‍🌈🏳️‍🌈✨

TL;DR #eMudhra root cause analysis still pending

https://emudhra.com/en/press-release/emudhra-statement-distrust-global-tls-intermediate-root-ca

RE: https://social.rust-lang.org/@rust/117478901936577572

woop, done quickly ✨️

PHP is actually short for Party Hard Project btw

Sometimes, while sounding very sublime and noble, you might be the jerk.

Passive-aggressive vaunt is usually a red flag.

Because of the #PHP shituation, I checked my web server logs a bit - only to see my alma mater appear:

185.73.23.168 - - [21/Oct/2026:08:51:53 +0000] "GET / HTTP/1.1" 502 150 "-" "Software Security Research/1.0 (+https://winston.softsec.ruhr-uni-bochum.de)" "-"

... oh wow, they started their HSM business in 1991.

https://www.cryptomuseum.com/manuf/utimaco/index.htm?hl=en-US

Maybe they could only generate single bytes back then. 🫠
(/s)

... ya know...

https://chaos.social/@fluepke/117474359589507276