<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Yestino - The Signal · RabbitMQ TLS</title><link>https://yestino.com/entities/rabbitmq-tls-eb87e6</link><description>Every event involving RabbitMQ TLS</description><language>en</language><atom:link href="https://yestino.com/entities/rabbitmq-tls-eb87e6/feed.xml" rel="self" type="application/rss+xml"/><item><title>How a RabbitMQ TLS mismatch burned one CPU core before AMQP negotiation</title><link>https://yestino.com/events/how-a-rabbitmq-tls-mismatch-burned-one-cpu-core-before-amqp-0dee7e</link><guid isPermaLink="true">https://yestino.com/events/how-a-rabbitmq-tls-mismatch-burned-one-cpu-core-before-amqp-0dee7e</guid><pubDate>Sun, 27 Sep 2026 12:27:00 GMT</pubDate><description>A production RabbitMQ TLS mismatch pinned one .NET thread to a CPU core.
Sources: Hacker Noon</description></item></channel></rss>