This error almost never means your certificate is broken. It means one side is speaking TLS and the other is answering in plaintext, and the mismatch shows…
| Bytes | Client reads as | Actual content |
|---|---|---|
48 54 54 50 |
record header | HTTP |
content type 0x48 |
not a valid TLS type | the letter H |
version 0x54 0x50 |
protocol version 84.80 | the letters TP |
Published on debugly.dev by Rohit Bhadani | Founder of Krova Cloud
A viral debate argues AI is not replacing SREs but deskilling them. Black-box tooling is eroding the debugging judgment that on-call needs.
Phorion found a backdoor in Claude Code 2.1.312 and 2.1.313 on Cursor Marketplace. It adds an SSH key and tries a reverse tunnel to 134.209.82.225.
OpenAI agents put two tasks in separate microVMs with no network and still traded secrets via CPU cache timing.
Kata Containers through 3.26.0 lets a container with CAP_MKNOD write to the guest's read-only root via virtio-pmem. 3.27.0 fixes it by moving to virtio-block.
