<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Howto defeat EU&#8217;s data retention act</title>
	<atom:link href="http://bitsex.net/english/2008/how-to-avoid-eu-data-retention-act/feed/" rel="self" type="application/rss+xml" />
	<link>http://bitsex.net/english/2008/how-to-avoid-eu-data-retention-act/</link>
	<description>Random stuff from a pseudorandom human</description>
	<pubDate>Tue, 06 Jan 2009 09:43:33 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: vidarlo</title>
		<link>http://bitsex.net/english/2008/how-to-avoid-eu-data-retention-act/comment-page-1/#comment-252</link>
		<dc:creator>vidarlo</dc:creator>
		<pubDate>Wed, 09 Jan 2008 06:43:59 +0000</pubDate>
		<guid isPermaLink="false">http://bitsex.net/uncategorized/2008/how-to-avoid-eu-data-retention-act/#comment-252</guid>
		<description>DeathBoy, could you elobarate on that? I did not write the text, but it seems quite googd enough for me.

As I gather the real thing is not encryption, but twarting traffic analysis to reveal whom is communicating.

And I can't see any really huge problems.</description>
		<content:encoded><![CDATA[<p>DeathBoy, could you elobarate on that? I did not write the text, but it seems quite googd enough for me.</p>
<p>As I gather the real thing is not encryption, but twarting traffic analysis to reveal whom is communicating.</p>
<p>And I can&#8217;t see any really huge problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DeathBoy</title>
		<link>http://bitsex.net/english/2008/how-to-avoid-eu-data-retention-act/comment-page-1/#comment-246</link>
		<dc:creator>DeathBoy</dc:creator>
		<pubDate>Tue, 08 Jan 2008 22:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://bitsex.net/uncategorized/2008/how-to-avoid-eu-data-retention-act/#comment-246</guid>
		<description>It's abundantly clear that you don't know the first thing about security or encryption.

I was passed this link by a friend, and I'm worried about how many people will read it and think it will make them somehow safer than leaving a note in a personals ad.

If you don't know what you're talking about, please don't make it even harder for the layman to understand by expounding such poorly put together ideas. This makes people's chances of security worse, not better.

Anyone digging this isn't helping, either.</description>
		<content:encoded><![CDATA[<p>It&#8217;s abundantly clear that you don&#8217;t know the first thing about security or encryption.</p>
<p>I was passed this link by a friend, and I&#8217;m worried about how many people will read it and think it will make them somehow safer than leaving a note in a personals ad.</p>
<p>If you don&#8217;t know what you&#8217;re talking about, please don&#8217;t make it even harder for the layman to understand by expounding such poorly put together ideas. This makes people&#8217;s chances of security worse, not better.</p>
<p>Anyone digging this isn&#8217;t helping, either.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Delay.no : Howto defeat EU’s data retention act</title>
		<link>http://bitsex.net/english/2008/how-to-avoid-eu-data-retention-act/comment-page-1/#comment-244</link>
		<dc:creator>Delay.no : Howto defeat EU’s data retention act</dc:creator>
		<pubDate>Mon, 07 Jan 2008 23:40:43 +0000</pubDate>
		<guid isPermaLink="false">http://bitsex.net/uncategorized/2008/how-to-avoid-eu-data-retention-act/#comment-244</guid>
		<description>[...] copied from http://bitsex.net/english/2008/how-to-avoid-eu-data-retention-act/ with [...]</description>
		<content:encoded><![CDATA[<p>[...] copied from <a href="http://bitsex.net/english/2008/how-to-avoid-eu-data-retention-act/" rel="nofollow" >http://bitsex.net/english/2008/how-to-avoid-eu-data-retention-act/</a> with [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AC</title>
		<link>http://bitsex.net/english/2008/how-to-avoid-eu-data-retention-act/comment-page-1/#comment-245</link>
		<dc:creator>AC</dc:creator>
		<pubDate>Mon, 07 Jan 2008 06:21:09 +0000</pubDate>
		<guid isPermaLink="false">http://bitsex.net/uncategorized/2008/how-to-avoid-eu-data-retention-act/#comment-245</guid>
		<description>Here's an implementation of a double-blind time-limited drop-box via DNS:
http://landonf.bikemonkey.org/code/security/DNS_Dead_Drop.20060128201048.26517.luxo.html

It's not undetectable -- the RD bit is not widely used -- but it's likely under the radar, especially if you use a DNS server located in another, non-cooperative country. Does tor support routing DNS queries out the network? That would be somewhat resilient to detection.

One nice thing about the methodology is that when posting the message, only '1' bits are observable. '0' bits are never sent, so try doing analysis on: 11111111111...

Retrieving the message, the 1s and 0s are (obviously) available, but your message is encrypted, right?</description>
		<content:encoded><![CDATA[<p>Here&#8217;s an implementation of a double-blind time-limited drop-box via DNS:<br />
<a href="http://landonf.bikemonkey.org/code/security/DNS_Dead_Drop.20060128201048.26517.luxo.html" rel="nofollow" onclick="javascript:urchinTracker ('/outbound/comment/landonf.bikemonkey.org');">http://landonf.bikemonkey.org/code/security/DNS_Dead_Drop.20060128201048.26517.luxo.html</a></p>
<p>It&#8217;s not undetectable &#8212; the RD bit is not widely used &#8212; but it&#8217;s likely under the radar, especially if you use a DNS server located in another, non-cooperative country. Does tor support routing DNS queries out the network? That would be somewhat resilient to detection.</p>
<p>One nice thing about the methodology is that when posting the message, only &#8216;1&#8242; bits are observable. &#8216;0&#8242; bits are never sent, so try doing analysis on: 11111111111&#8230;</p>
<p>Retrieving the message, the 1s and 0s are (obviously) available, but your message is encrypted, right?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
