<?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: Beware of free wifi hotspots</title>
	<atom:link href="http://www.kayodemuyibi.com/beware-of-free-wifi-hotspots/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kayodemuyibi.com/beware-of-free-wifi-hotspots/</link>
	<description>Kazey Journal</description>
	<lastBuildDate>Mon, 12 Dec 2011 11:14:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Robbie Honerkamp</title>
		<link>http://www.kayodemuyibi.com/beware-of-free-wifi-hotspots/#comment-24460</link>
		<dc:creator>Robbie Honerkamp</dc:creator>
		<pubDate>Thu, 13 Mar 2008 19:44:18 +0000</pubDate>
		<guid isPermaLink="false">http://kayodemuyibi.com/2007/09/03/beware-of-free-wifi-hotspots/#comment-24460</guid>
		<description>Good points, but..

There are some concerns with Tor. Exit nodes on Tor shouldn&#039;t be considered safe, and if you&#039;re sending unencrypted traffic over Tor, there&#039;s a decent chance that a malicious exit node could be sniffing your traffic. Late last year, several suspicious exit nodes were found that specifically only accepted unencrypted traffic. Some details about it are here:

http://czarism.com/tor-vs-security-sniffing-exit-nodes

Another issue with open wifi access points are malicious nodes that may be set up in popular areas (cities, near universities, coffee shops, etc) by someone who sniffs all the _ethernet_ traffic coming out of his access point.

In short, make sure important traffic is encrypted (POP/IMAP mail, https banking sites). While even this can be broken by a carefully crafted man-in-the-middle attack, there&#039;s so much easily intercepted unencrypted stuff floating around out there that hackers won&#039;t bother with your encrypted traffic.</description>
		<content:encoded><![CDATA[<p>Good points, but..</p>
<p>There are some concerns with Tor. Exit nodes on Tor shouldn&#8217;t be considered safe, and if you&#8217;re sending unencrypted traffic over Tor, there&#8217;s a decent chance that a malicious exit node could be sniffing your traffic. Late last year, several suspicious exit nodes were found that specifically only accepted unencrypted traffic. Some details about it are here:</p>
<p><a href="http://czarism.com/tor-vs-security-sniffing-exit-nodes" rel="nofollow">http://czarism.com/tor-vs-security-sniffing-exit-nodes</a></p>
<p>Another issue with open wifi access points are malicious nodes that may be set up in popular areas (cities, near universities, coffee shops, etc) by someone who sniffs all the _ethernet_ traffic coming out of his access point.</p>
<p>In short, make sure important traffic is encrypted (POP/IMAP mail, https banking sites). While even this can be broken by a carefully crafted man-in-the-middle attack, there&#8217;s so much easily intercepted unencrypted stuff floating around out there that hackers won&#8217;t bother with your encrypted traffic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Labelle</title>
		<link>http://www.kayodemuyibi.com/beware-of-free-wifi-hotspots/#comment-17649</link>
		<dc:creator>Labelle</dc:creator>
		<pubDate>Wed, 05 Sep 2007 15:37:04 +0000</pubDate>
		<guid isPermaLink="false">http://kayodemuyibi.com/2007/09/03/beware-of-free-wifi-hotspots/#comment-17649</guid>
		<description>hmm...thanks for the lesson...use free wi-fi spots all d time...am aware of some sniffing idiot banging in on my info..but i sorta ignore the thot...but this helps. tnx!</description>
		<content:encoded><![CDATA[<p>hmm&#8230;thanks for the lesson&#8230;use free wi-fi spots all d time&#8230;am aware of some sniffing idiot banging in on my info..but i sorta ignore the thot&#8230;but this helps. tnx!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

