ppl always complain that the clock on my microwave never shows the right time bcs i cant be assed to set it manually
so now i have an unfuck-microwave.sh cronjob which briefly kills its power every day at midnight
Inspired by the classic xeyes program, I made a thing:
ssh teyes.fly.dev
Or go install github.com/mcpherrinm/teyes@latest && teyes
Give your mouse a wiggle over the terminal!
I'll be speaking at the Ontario Cryptography Day!
https://ontario-crypto-day.github.io/
Where: University of Waterloo Davis Centre (DC) 1301 and 1302
When: Friday, June 6, 2025, from 10am to approx. 4:30pm
I hope anyone in the area interested in cryptography is able to attend. It's a free event, but registration is required.
@rsalz interesting that the criteria is in ALL root stores, which might be an issue in some cases as root stores evolved.
Eg, a new CA that's trusted directly in Chrome, with a cross-sign from an old CA. Perhaps Chrome only trusts the new CA, and some other program like Microsoft (who aren't taking new roots right now) only supports the old CA providing the cross-sign.
A certificate chain with the cross-sign will work with both programs, but Akamai's policy here seems like it may exclude said CA.
Earlier this year we announced our intention to introduce short-lived certificates with lifetimes of six days as an option for our subscribers. Yesterday we issued our first short-lived certificate. You can see the certificate at the bottom of our post, or here thanks to Certificate Transparency logs. We issued it to ourselves and then immediately revoked it so we can observe the certificate’s whole lifecycle. This is the first step towards making short-lived certificates available to all subscribers.