<?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"
	>
<channel>
	<title>Comments on: Understanding Phishing Scams&#8230;first hand!</title>
	<atom:link href="http://weblog.techdad.net/2006/09/29/understanding-phishing-scamsfirst-hand/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblog.techdad.net/2006/09/29/understanding-phishing-scamsfirst-hand/</link>
	<description>...where technology and fatherhood collide...</description>
	<pubDate>Thu, 20 Nov 2008 13:41:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: TechDadBlog &#187; Blog Archive &#187; ALERT: LogMeIn Phishing Scam claims New Encryption</title>
		<link>http://weblog.techdad.net/2006/09/29/understanding-phishing-scamsfirst-hand/#comment-3534</link>
		<dc:creator>TechDadBlog &#187; Blog Archive &#187; ALERT: LogMeIn Phishing Scam claims New Encryption</dc:creator>
		<pubDate>Wed, 07 Nov 2007 16:41:56 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.techdad.net/?p=36#comment-3534</guid>
		<description>[...] to get users to put in their LogMeIn information. (I have covered Phishing scams before. See posts #1, #2 and #3.) This is a very big concern to any LogMeIn users since this essentially gives the [...]</description>
		<content:encoded><![CDATA[<p>[...] to get users to put in their LogMeIn information. (I have covered Phishing scams before. See posts #1, #2 and #3.) This is a very big concern to any LogMeIn users since this essentially gives the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://weblog.techdad.net/2006/09/29/understanding-phishing-scamsfirst-hand/#comment-260</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Thu, 04 Jan 2007 01:59:40 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.techdad.net/?p=36#comment-260</guid>
		<description>Not sure if the user above is truly the "Marcis" who appeared in the WHOIS...and I'm not too sure I understand the nature of the post. I don't know what that the IP was when that site was up. If I encounter one again, that is probably a good thing to grab. If your site was highjacked by someone for this phishing scam, I'm sorry to hear that.</description>
		<content:encoded><![CDATA[<p>Not sure if the user above is truly the &#8220;Marcis&#8221; who appeared in the WHOIS&#8230;and I&#8217;m not too sure I understand the nature of the post. I don&#8217;t know what that the IP was when that site was up. If I encounter one again, that is probably a good thing to grab. If your site was highjacked by someone for this phishing scam, I&#8217;m sorry to hear that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcis</title>
		<link>http://weblog.techdad.net/2006/09/29/understanding-phishing-scamsfirst-hand/#comment-250</link>
		<dc:creator>Marcis</dc:creator>
		<pubDate>Sat, 30 Dec 2006 18:15:50 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.techdad.net/?p=36#comment-250</guid>
		<description>Listen, I would like to know what IP was there at the moment. As I am the domain owner I didn't knew who was using it as at that time I was moving in UK. Any information would be needed as the Domain provider deleted my domain aswell.

Thanks.</description>
		<content:encoded><![CDATA[<p>Listen, I would like to know what IP was there at the moment. As I am the domain owner I didn&#8217;t knew who was using it as at that time I was moving in UK. Any information would be needed as the Domain provider deleted my domain aswell.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://weblog.techdad.net/2006/09/29/understanding-phishing-scamsfirst-hand/#comment-18</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Wed, 11 Oct 2006 22:59:04 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.techdad.net/?p=36#comment-18</guid>
		<description>It looks like the domain has been taken down! So, one less "danger" out on the web!</description>
		<content:encoded><![CDATA[<p>It looks like the domain has been taken down! So, one less &#8220;danger&#8221; out on the web!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
