Website | Schmiedecker.net |
Website | Schmiedecker.net |
Good news, the Tuscolo CT logs are now "Qualified" (meaning that some of your certs are/will soon be using our CT log!!)
The bad news is that by including our new logs in the well known list of CT logs, some stuff now instantly crashes (seemingly because the array of non "Sunlight" (aka next gen) logs is empty).
Impacted things seem to include:
1. 80% of the food delivery app market in Brazil
2. Lots of banks in India
3. Lowes????
4. Basically any app that uses appmattus/certificatetransparency
Suboptimal.
More info:
1. https://github.com/appmattus/certificatetransparency/issues/143
2. https://github.com/google/certificate-transparency-go/issues/1712
The street that my mum lives in is a one-way street, but wasn't marked as such on #Google Maps. This caused many drivers to drive the wrong way. I have tried to edit it on Google Maps (there is such functionality), but to no avail. No matter how often I submitted a change (with photos of street signs!), Google said "Sorry, we could not verify it".
Solution: Edit the street on #OpenStreetMap! A few months after I did this, Google seems to have stolen the data, as it regularly does, and now the street is correct in both datasets!
Here's something I am very excited about: Photosynthesis! 🌱☀️
A proposal to have CAs run transparency logs and make X.509 certificates out of Merkle Tree inclusion proofs.
This is similar to how CT would have worked in an ideal world, and it solves the problem of PQC signature sizes in logs and handshakes.
https://mailarchive.ietf.org/arch/msg/tls/6jqhUVz58s4ZgsZ8HvuZftncT9A/
Do you enjoy guzzling real-time TLS certificate allocations, but don't want to use a third-party service (crt.sh, CertStream, etc.)? Drink straight from the Certificate Transparency log firehose using ctail:
$ go run github.com/hdm/ctail@latest -f -m '^autodiscover\.'