<?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: Scams - New and Not-So-New</title>
	<atom:link href="http://www.chrystalline.com/2008/02/scams-new-and-not-so-new/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.chrystalline.com/2008/02/scams-new-and-not-so-new/</link>
	<description>The Sparkly Purple Vanilla Girl</description>
	<pubDate>Fri, 05 Dec 2008 10:40:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: Chrystalline</title>
		<link>http://www.chrystalline.com/2008/02/scams-new-and-not-so-new/#comment-263</link>
		<dc:creator>Chrystalline</dc:creator>
		<pubDate>Mon, 24 Mar 2008 02:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrystalline.com/2008/02/scams-new-and-not-so-new/#comment-263</guid>
		<description>Ah, I can't believe I overlooked that! I know about SSL, and I completely forgot that part. I did forward the one I got to BOA - figured they'd want to know about it so they could take whatever steps are available to them.

I didn't have the nerve to click the link, though I don't even have a BOA account to risk.  Anyway, good to know I'm not the only one seeing the danger in this one.

(BTW - stuck some spaces in to make it stop hyperlinking those URLs - no need to make it easy for people to blunder into it.)</description>
		<content:encoded><![CDATA[<p>Ah, I can&#8217;t believe I overlooked that! I know about SSL, and I completely forgot that part. I did forward the one I got to BOA - figured they&#8217;d want to know about it so they could take whatever steps are available to them.</p>
<p>I didn&#8217;t have the nerve to click the link, though I don&#8217;t even have a BOA account to risk.  Anyway, good to know I&#8217;m not the only one seeing the danger in this one.</p>
<p>(BTW - stuck some spaces in to make it stop hyperlinking those URLs - no need to make it easy for people to blunder into it.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Killen</title>
		<link>http://www.chrystalline.com/2008/02/scams-new-and-not-so-new/#comment-262</link>
		<dc:creator>Larry Killen</dc:creator>
		<pubDate>Mon, 24 Mar 2008 00:15:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.chrystalline.com/2008/02/scams-new-and-not-so-new/#comment-262</guid>
		<description>I just received the BOA Cert notice.  My suspicions were arroused when I noticed the URL they reference was an HTTP rather than HTTPS.  ALL security type data would ALWAYS be sent over a secured socket layer.  Upon examining the source, I noticed that the destination URL was not the same as the published URL.  There may very well be an http: // direct-certs.bankofamerica. com/direct/certpickup.asp? but if you were to click on it (DON'T), you would go to http: // direct-certs.bankofamerica. com.avtthompson.hu.com/direct/certpickup.asp?

I also examined the mail header and the mail is actually from :
Received: from altern.org (unknown [37.15.39.134])
     by the69vamps.com with SMTP id EVF6AO2XP7

And to top it off, I get the mail on Easter Sunday.</description>
		<content:encoded><![CDATA[<p>I just received the BOA Cert notice.  My suspicions were arroused when I noticed the URL they reference was an HTTP rather than HTTPS.  ALL security type data would ALWAYS be sent over a secured socket layer.  Upon examining the source, I noticed that the destination URL was not the same as the published URL.  There may very well be an http: // direct-certs.bankofamerica. com/direct/certpickup.asp? but if you were to click on it (DON&#8217;T), you would go to http: // direct-certs.bankofamerica. com.avtthompson.hu.com/direct/certpickup.asp?</p>
<p>I also examined the mail header and the mail is actually from :<br />
Received: from altern.org (unknown [37.15.39.134])<br />
     by the69vamps.com with SMTP id EVF6AO2XP7</p>
<p>And to top it off, I get the mail on Easter Sunday.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
