<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>An Insight to Covert Channels · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/1306.2252/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/1306.2252/feed.xml" rel="self" type="application/rss+xml" /><item><title>An Insight to Covert Channels — mentioned by nickpsecurity</title><link>https://news.ycombinator.com/item?id=14017812</link><guid isPermaLink="false">urn:hackerpapers:mention:1306.2252:14017812</guid><pubDate>Sun, 02 Apr 2017 16:53:10 GMT</pubDate><description>&lt;p&gt;Good to see you, Ian! Yeah, there was a recent post on Lobsters with a pile of progress on tech you sent me a while back. Them getting an AOT can help so long as you can get a good, mental idea of what the assembly is going to be doing for a given piece of Java. Otherwise, you&amp;#x27;ll be doing a lot of rewriting that might make one reconsider Java in first place. Pluggable GC&amp;#x27;s is a good think as is ability to turn it off for unsafe native. You told me before they could do the latter, probably were for some of the platform. Before answering the other question, it helps to understand what covert…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/1306.2252/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.CR</category></item></channel></rss>
