<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: olegarch</title><link>https://news.ycombinator.com/user?id=olegarch</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Sun, 08 Nov 2026 16:28:04 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=olegarch" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by olegarch in "Encrypted traffic interception on Hetzner and Linode targeting Jabber service"]]></title><description><![CDATA[
<p>Using DANE or so (RRs CAA/TLSA) can help in this case (when provider route traffic to specific port), but does not solve the problem completely. 
If DNS record will be compromised, then hacker can setup "correct" TLSA/CAA record to trust his fake certificate.
As result, problem can be solved, if we will have reliable DNS subsystem, where is impossible to compromise DNS provider or infrastructure.<p>I think, emerDNS can be used in such critical application: <a href="https://emercoin.com/en/documentation/blockchain-services/emerdns/emerdns-introduction/" rel="nofollow noreferrer">https://emercoin.com/en/documentation/blockchain-services/em...</a></p>
]]></description><pubDate>Sat, 21 Oct 2023 14:59:54 +0000</pubDate><link>https://news.ycombinator.com/item?id=37967343</link><dc:creator>olegarch</dc:creator><comments>https://news.ycombinator.com/item?id=37967343</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=37967343</guid></item></channel></rss>