<?xml version="1.0" encoding="UTF-8"?> <rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/"
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/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
> <channel><title>gHacks Technology News &#124; Latest Tech News, Software And Tutorials &#187; masquerade</title> <atom:link href="http://www.ghacks.net/tag/masquerade/feed/" rel="self" type="application/rss+xml" /><link>http://www.ghacks.net</link> <description>A technology news blog covering software, mobile phones, gadgets, security, the Internet and other relevant areas.</description> <lastBuildDate>Sat, 11 Feb 2012 17:32:23 +0000</lastBuildDate> <language>en</language> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>http://wordpress.org/?v=3.3.1</generator> <atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/> <item><title>Anatomy of a failed virus attack</title><link>http://www.ghacks.net/2005/12/07/anatomy-of-a-failed-virus-attack/</link> <comments>http://www.ghacks.net/2005/12/07/anatomy-of-a-failed-virus-attack/#comments</comments> <pubDate>Wed, 07 Dec 2005 08:16:12 +0000</pubDate> <dc:creator>Martin Brinkmann</dc:creator> <category><![CDATA[Email]]></category> <category><![CDATA[Knowledge]]></category> <category><![CDATA[email header]]></category> <category><![CDATA[fake mail]]></category> <category><![CDATA[masquerade]]></category> <category><![CDATA[scam]]></category> <category><![CDATA[trojan]]></category> <category><![CDATA[virus]]></category> <category><![CDATA[worm]]></category> <guid
isPermaLink="false">http://www.ghacks.net/?p=2</guid> <description><![CDATA[Jim Kissel of Open Source Migrations Limited wrote a nice article about a malicious email attack he encountered recently. He analyzes the email received and gives tips to secure Thunderbird, the free email program they use. ]]></description> <content:encoded><![CDATA[<p><a
href="http://www.theregister.co.uk/2005/12/06/failed_virus_attack/">Jim Kissel</a> of Open Source Migrations Limited wrote a nice article about a malicious email attack he encountered recently. He analyzes the email he received and gives tips to secure Thunderbird, the free email program he uses.</p><p>The interesting part is the analysis of the mail.  He dissects every part of the message and of course takes a look at the email header as well. The analysis ends with an advice (which he puts at the beginning of his essay) which should be common sense nowadays.</p><p><span
id="more-2"></span>1.  You need effective technology to protect you from the many unscrupulous people out there on the Internet who want to damage your systems, scam you or generally subvert your computing resources for their own ends.</p><p>2. Security via technology alone is not sufficient to combat the cyber criminals who are out to get you, your business, and your computers.  You need to be aware of what is going on around you and take control of the situation before you are compromised.  Just as Ignorance of the law is no excuse,  ignorance of your computing environment can also land you in deep trouble.</p><p>My personal suggestion for you is to switch to a secure email program if you are still using Microsoft outlook. Mozilla Thunderbird, Opera Email and many others are not attacked that often and have better options to improve security.</p><p>The suggestions that follow are all important, back then and today as well. Kissel suggests to turn of JavaScript to block that attack vector, block the loading of remote elements like images which can for instance be used for tracking purposes or expoits, use secure connections via SSL when retrieving and sending email, and viewing emails only in plain text and not HTML.</p> ]]></content:encoded> <wfw:commentRss>http://www.ghacks.net/2005/12/07/anatomy-of-a-failed-virus-attack/feed/</wfw:commentRss> <slash:comments>1</slash:comments> </item> </channel> </rss>
