🜗 🝒 🝲 crypto as in 'cryptography' 🝳 🝡 🜖
¹ isogenist, co-host SCWpod
² https://durumcrustulum.com, https://www.youtube.com/@durumcrustulum
Deirdre Connolly¹ ²
Loading...
Ulmo rocks
BBC got a crew into southern Lebanon — Israel’s “security zone.”
All buildings are gone.
All houses are gone.
All humans are gone.
The only thing that stands above the rubble is an Israeli flag.
www.bbc.com/news/videos/...
I wrote about SpaceX. SpaceX the rocket company, SpaceX the suspicious financial instrument for Musk to create value out of thin air. SpaceX the meme. SpaceX as the 7-headed hydra at the end of capitalism. (gift link) www.theatlantic.com/technology/2...
this is very cool and so very Catholic of Tolkien:
youtu.be/c-YIwTG3wPo
Ughhhhh this is requiring a bunch of changes, because removing signature_algorithms_cert makes it default to signature_algorithms, so I need to expand it, so I can't assume it's a list of supported sigalgs, and I need to consider how it will break other legacy clients.
There would have been responsible ways to write that rule, by the way. For example, by making it turn itself off after a few months if not updated.
Palo Alto has no incentive not to harm the Internet or their customers though, because IDS/IPS are usually mandated.
In 2020, OpenSSL had a vuln related to the signature_algorithms_cert ext. openssl-library.org/news/secadv/...
Palo Alto apparently "solved" this in their IPS by blocking connections with "unknown" algs in sigalg_cert.
Six years later, we can't add ML-DSA to sigalg_cert in Go. sigalg_cert is dead.
