<?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 for Shades of Gray Security</title>
	<atom:link href="http://shadesofgraysecurity.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://shadesofgraysecurity.com</link>
	<description>Because security isn't always black &#38; white</description>
	<lastBuildDate>Tue, 08 Nov 2011 17:44:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>Comment on Password Primer by Jason Ingalls</title>
		<link>http://shadesofgraysecurity.com/password-primer/comment-page-1/#comment-3803</link>
		<dc:creator>Jason Ingalls</dc:creator>
		<pubDate>Tue, 08 Nov 2011 17:44:22 +0000</pubDate>
		<guid isPermaLink="false">http://shadesofgraysecurity.com/?p=220#comment-3803</guid>
		<description>Excellent article.  One thing I might add is to reinforce the idea that folks shouldn&#039;t reuse passwords.  If you use an email provider on the web, Facebook, or other website that allows you to log in without encrypting the traffic between you and their server, this could spell disaster if your password for that service is shared with other accounts.  Here&#039;s how:

Let&#039;s say I&#039;m a sneaky bad guy.  I spend time in hotels/airports/Starbucks and anywhere else there is unsecured (unencrypted) wireless, just sniffing the traffic that&#039;s going between your laptop and the Wireless Access Point you are using to get on the Internet to go to, say, Facebook.  I watch you log on to Facebook, and I get the username and the password that you send to Facebook because it&#039;s not encrypted.  Or I watch you log into GMail, and get your username and password the same way.  What matters is I now know your account information.

Another major concern is that by using the same password for all of your accounts on all of the various services you log into on the Internet, you are trusting each service equally.  Do you think that your Neighborhood Association&#039;s website should be trusted with the same amount of responsibility to keep your password safely stored as your bank? I hope not, but if you use the same password for both of them, it means that they are.  

Some services are not well secured, and that means that if bad guys managed to hack into a weaker site that has the same password you use for everything else, everything else is just as vulnerable for you as the site that just got hacked.  Bad ju ju.

If you use one password to log into everything, and I capture it, I can use it to log into everything you do.  Never use the same password to log into two or more systems.

-Jason</description>
		<content:encoded><![CDATA[<p>Excellent article.  One thing I might add is to reinforce the idea that folks shouldn&#8217;t reuse passwords.  If you use an email provider on the web, Facebook, or other website that allows you to log in without encrypting the traffic between you and their server, this could spell disaster if your password for that service is shared with other accounts.  Here&#8217;s how:</p>
<p>Let&#8217;s say I&#8217;m a sneaky bad guy.  I spend time in hotels/airports/Starbucks and anywhere else there is unsecured (unencrypted) wireless, just sniffing the traffic that&#8217;s going between your laptop and the Wireless Access Point you are using to get on the Internet to go to, say, Facebook.  I watch you log on to Facebook, and I get the username and the password that you send to Facebook because it&#8217;s not encrypted.  Or I watch you log into GMail, and get your username and password the same way.  What matters is I now know your account information.</p>
<p>Another major concern is that by using the same password for all of your accounts on all of the various services you log into on the Internet, you are trusting each service equally.  Do you think that your Neighborhood Association&#8217;s website should be trusted with the same amount of responsibility to keep your password safely stored as your bank? I hope not, but if you use the same password for both of them, it means that they are.  </p>
<p>Some services are not well secured, and that means that if bad guys managed to hack into a weaker site that has the same password you use for everything else, everything else is just as vulnerable for you as the site that just got hacked.  Bad ju ju.</p>
<p>If you use one password to log into everything, and I capture it, I can use it to log into everything you do.  Never use the same password to log into two or more systems.</p>
<p>-Jason</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Security from Obscurity: Building a Security Program, Define the Domain by Caiya</title>
		<link>http://shadesofgraysecurity.com/building-security-program-part2/comment-page-1/#comment-2555</link>
		<dc:creator>Caiya</dc:creator>
		<pubDate>Fri, 15 Jul 2011 06:09:33 +0000</pubDate>
		<guid isPermaLink="false">http://shadesofgraysecurity.com/?p=160#comment-2555</guid>
		<description>It&#039;s much easier to unesdtrand when you put it that way!</description>
		<content:encoded><![CDATA[<p>It&#8217;s much easier to unesdtrand when you put it that way!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Security from Obscurity: Building a Security Program, Define the Domain by Security from Obscurity: Building a Security Program, Understanding the Standards &#124; Shades of Gray Security</title>
		<link>http://shadesofgraysecurity.com/building-security-program-part2/comment-page-1/#comment-112</link>
		<dc:creator>Security from Obscurity: Building a Security Program, Understanding the Standards &#124; Shades of Gray Security</dc:creator>
		<pubDate>Thu, 18 Mar 2010 23:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://shadesofgraysecurity.com/?p=160#comment-112</guid>
		<description>[...] about a few different standards, and focus on the one you most likely should start with. In the last installment we touched on ISO 17799. This is probably the best place to start to build a security program. [...]</description>
		<content:encoded><![CDATA[<p>[...] about a few different standards, and focus on the one you most likely should start with. In the last installment we touched on ISO 17799. This is probably the best place to start to build a security program. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Contact Us by Security from Obscurity: Building a Security Program, Define the Domain &#124; Shades of Gray Security</title>
		<link>http://shadesofgraysecurity.com/about/contact/comment-page-1/#comment-41</link>
		<dc:creator>Security from Obscurity: Building a Security Program, Define the Domain &#124; Shades of Gray Security</dc:creator>
		<pubDate>Tue, 15 Sep 2009 00:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://shadesofgraysecurity.com/?page_id=141#comment-41</guid>
		<description>[...] Contact Us [...]</description>
		<content:encoded><![CDATA[<p>[...] Contact Us [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Security from Obscurity: Building a Security Program, Intro by Security from Obscurity: Building a Security Program, Define the Domain &#124; Shades of Gray Security</title>
		<link>http://shadesofgraysecurity.com/building-security-program-part1/comment-page-1/#comment-40</link>
		<dc:creator>Security from Obscurity: Building a Security Program, Define the Domain &#124; Shades of Gray Security</dc:creator>
		<pubDate>Tue, 15 Sep 2009 00:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://shadesofgraysecurity.com/?p=106#comment-40</guid>
		<description>[...] our first installment, we decided who needs to be involved in the program and an idea of how it is structured and to whom [...]</description>
		<content:encoded><![CDATA[<p>[...] our first installment, we decided who needs to be involved in the program and an idea of how it is structured and to whom [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Contact Us by building a security program from scratch &#124; Shades of Gray Security</title>
		<link>http://shadesofgraysecurity.com/about/contact/comment-page-1/#comment-37</link>
		<dc:creator>building a security program from scratch &#124; Shades of Gray Security</dc:creator>
		<pubDate>Mon, 07 Sep 2009 17:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://shadesofgraysecurity.com/?page_id=141#comment-37</guid>
		<description>[...] Contact Us [...]</description>
		<content:encoded><![CDATA[<p>[...] Contact Us [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Killing bugs, a Social Engineering Odyssey by Killing Bugs, a Social Engineering Odyssey &#124; DC225</title>
		<link>http://shadesofgraysecurity.com/killing-bugs-social-engineering-odyssey/comment-page-1/#comment-11</link>
		<dc:creator>Killing Bugs, a Social Engineering Odyssey &#124; DC225</dc:creator>
		<pubDate>Wed, 24 Jun 2009 20:04:24 +0000</pubDate>
		<guid isPermaLink="false">http://shadesofgraysecurity.com/?p=36#comment-11</guid>
		<description>[...] continued at social engineering true story &#8211; Shades of Gray Security.    Tags infosec&#8226; social engineering    Leave a Reply  Click here to cancel [...]</description>
		<content:encoded><![CDATA[<p>[...] continued at social engineering true story &#8211; Shades of Gray Security.    Tags infosec&bull; social engineering    Leave a Reply  Click here to cancel [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on No Firewalls for Stupid by Chuck</title>
		<link>http://shadesofgraysecurity.com/no-firewalls-for-stupid/comment-page-1/#comment-10</link>
		<dc:creator>Chuck</dc:creator>
		<pubDate>Wed, 24 Jun 2009 18:26:17 +0000</pubDate>
		<guid isPermaLink="false">http://shadesofgraysecurity.com/?p=5#comment-10</guid>
		<description>That being said... I love stupid people.  They generally keep me employed.</description>
		<content:encoded><![CDATA[<p>That being said&#8230; I love stupid people.  They generally keep me employed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on No Firewalls for Stupid by Twisted</title>
		<link>http://shadesofgraysecurity.com/no-firewalls-for-stupid/comment-page-1/#comment-9</link>
		<dc:creator>Twisted</dc:creator>
		<pubDate>Wed, 24 Jun 2009 16:28:48 +0000</pubDate>
		<guid isPermaLink="false">http://shadesofgraysecurity.com/?p=5#comment-9</guid>
		<description>As long as there are people excited to get greeting cards for no particular reason, from people they don&#039;t even know, there will always be people fighting Conficker. &quot;I&#039;m sorry Mr. CEO, that wasn&#039;t a stranger showing you some unexpected love, that was a virus. You lose one internets.&quot;</description>
		<content:encoded><![CDATA[<p>As long as there are people excited to get greeting cards for no particular reason, from people they don&#8217;t even know, there will always be people fighting Conficker. &#8220;I&#8217;m sorry Mr. CEO, that wasn&#8217;t a stranger showing you some unexpected love, that was a virus. You lose one internets.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on No Firewalls for Stupid by Chuck</title>
		<link>http://shadesofgraysecurity.com/no-firewalls-for-stupid/comment-page-1/#comment-8</link>
		<dc:creator>Chuck</dc:creator>
		<pubDate>Wed, 24 Jun 2009 15:31:56 +0000</pubDate>
		<guid isPermaLink="false">http://shadesofgraysecurity.com/?p=5#comment-8</guid>
		<description>Great site!  All the security in the world doesn&#039;t prevent someone from doing something stupid.  You can usually mitigate stupid at the end user level, but once it travels too far up the chain it&#039;s over.  I&#039;m still amazed that people are still fighting with things like Conficker even though it&#039;s basically been defeated months ago.</description>
		<content:encoded><![CDATA[<p>Great site!  All the security in the world doesn&#8217;t prevent someone from doing something stupid.  You can usually mitigate stupid at the end user level, but once it travels too far up the chain it&#8217;s over.  I&#8217;m still amazed that people are still fighting with things like Conficker even though it&#8217;s basically been defeated months ago.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

