<?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: Why Security Isn&#8217;t</title>
	<atom:link href="http://g33q.co.za/2008/07/13/why-security-isnt/feed/" rel="self" type="application/rss+xml" />
	<link>http://g33q.co.za/2008/07/13/why-security-isnt/</link>
	<description>The New Look Tech Blog</description>
	<lastBuildDate>Tue, 15 May 2012 17:00:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Quintin</title>
		<link>http://g33q.co.za/2008/07/13/why-security-isnt/comment-page-1/#comment-83</link>
		<dc:creator>Quintin</dc:creator>
		<pubDate>Sun, 20 Jul 2008 10:47:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.g33q.co.za/?p=54#comment-83</guid>
		<description>HAH! And just to prove my point an aide to the British PM lost his Blackberry in Shanghai. It was not encrypted and was secured by only a password.

Turns out the dude was shagging a Chinese spy after she picked him up in a nightclub and she stole it.

Oy...</description>
		<content:encoded><![CDATA[<p>HAH! And just to prove my point an aide to the British PM lost his Blackberry in Shanghai. It was not encrypted and was secured by only a password.</p>
<p>Turns out the dude was shagging a Chinese spy after she picked him up in a nightclub and she stole it.</p>
<p>Oy&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaco Kroon</title>
		<link>http://g33q.co.za/2008/07/13/why-security-isnt/comment-page-1/#comment-82</link>
		<dc:creator>Jaco Kroon</dc:creator>
		<pubDate>Fri, 18 Jul 2008 20:12:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.g33q.co.za/?p=54#comment-82</guid>
		<description>When you&#039;re in a position where you need to &quot;remember&quot; 50+ passwords and have access to it at all times you don&#039;t have too many options.  There exists an alternative solution for me fortunately:  ssh keys.</description>
		<content:encoded><![CDATA[<p>When you&#8217;re in a position where you need to &#8220;remember&#8221; 50+ passwords and have access to it at all times you don&#8217;t have too many options.  There exists an alternative solution for me fortunately:  ssh keys.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quintin</title>
		<link>http://g33q.co.za/2008/07/13/why-security-isnt/comment-page-1/#comment-81</link>
		<dc:creator>Quintin</dc:creator>
		<pubDate>Fri, 18 Jul 2008 20:09:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.g33q.co.za/?p=54#comment-81</guid>
		<description>Yep. I am currently busy memorizing as many of those passwords as I can. BTW that was lying around the office and I need to destroy it.

Good spot though.</description>
		<content:encoded><![CDATA[<p>Yep. I am currently busy memorizing as many of those passwords as I can. BTW that was lying around the office and I need to destroy it.</p>
<p>Good spot though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stealthyninja</title>
		<link>http://g33q.co.za/2008/07/13/why-security-isnt/comment-page-1/#comment-80</link>
		<dc:creator>stealthyninja</dc:creator>
		<pubDate>Fri, 18 Jul 2008 19:01:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.g33q.co.za/?p=54#comment-80</guid>
		<description>I tend to prefer my passwords as long phrases and sentences sprinkled with some uppercase characters, deliberate spelling mistakes to confound dictionary attacks, numbers and a punctuation mark or two. Naturally the complexity of a password goes up/down depending on what ever it is for.

The idea is to never make them hard to remember or hard to type once known, especially if a number of people for what ever reason need access to the same account and password since then lists become an unfortunate necessity. By the way, a hard copy of said list kept in a laptop bag left relatively unattended in an office strikes me as even worse than keeping it somewhere on a network share. ;-P</description>
		<content:encoded><![CDATA[<p>I tend to prefer my passwords as long phrases and sentences sprinkled with some uppercase characters, deliberate spelling mistakes to confound dictionary attacks, numbers and a punctuation mark or two. Naturally the complexity of a password goes up/down depending on what ever it is for.</p>
<p>The idea is to never make them hard to remember or hard to type once known, especially if a number of people for what ever reason need access to the same account and password since then lists become an unfortunate necessity. By the way, a hard copy of said list kept in a laptop bag left relatively unattended in an office strikes me as even worse than keeping it somewhere on a network share. ;-P</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaco Kroon</title>
		<link>http://g33q.co.za/2008/07/13/why-security-isnt/comment-page-1/#comment-79</link>
		<dc:creator>Jaco Kroon</dc:creator>
		<pubDate>Wed, 16 Jul 2008 05:09:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.g33q.co.za/?p=54#comment-79</guid>
		<description>Just some backing for what you&#039;re saying.

http://crimelert.co.za/latest/got-a-wireless-network-fbi-alert.html</description>
		<content:encoded><![CDATA[<p>Just some backing for what you&#8217;re saying.</p>
<p><a href="http://crimelert.co.za/latest/got-a-wireless-network-fbi-alert.html" rel="nofollow">http://crimelert.co.za/latest/got-a-wireless-network-fbi-alert.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quintin</title>
		<link>http://g33q.co.za/2008/07/13/why-security-isnt/comment-page-1/#comment-78</link>
		<dc:creator>Quintin</dc:creator>
		<pubDate>Sun, 13 Jul 2008 19:17:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.g33q.co.za/?p=54#comment-78</guid>
		<description>Ah, I forgot the whole prefix thing. I actually wanted to add this to point 3 on the first list, and forgot...

Luckily you pointed that out.

Prefixes are a very helpful tool, and one of the best security tips I came across recently.</description>
		<content:encoded><![CDATA[<p>Ah, I forgot the whole prefix thing. I actually wanted to add this to point 3 on the first list, and forgot&#8230;</p>
<p>Luckily you pointed that out.</p>
<p>Prefixes are a very helpful tool, and one of the best security tips I came across recently.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jaco Kroon</title>
		<link>http://g33q.co.za/2008/07/13/why-security-isnt/comment-page-1/#comment-77</link>
		<dc:creator>Jaco Kroon</dc:creator>
		<pubDate>Sun, 13 Jul 2008 18:47:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.g33q.co.za/?p=54#comment-77</guid>
		<description>Regarding point 3 in the first list.  There are some routers that only supports WEP.  And yea, I even have a wireless card that cannot do 128-bit WEP, only 64-bit.  Go figure what these people were thinking considering that a decently fast machine could crack DES (A 56-bit encryption algorithm masquerading as 64-bit) in approximately an hour in 2004 already.  For every bit you add, the time theoretically doubles.

Regarding your practices, what helps for passwords, and if you must have lists, use a combination password.  In other words, have a prefix that is really hard to guess that you keep constant for all your machines, and then a suffix which is unique for each machine/purpose.  You should still decide who to trust with what and preferably have multiple prefixes for different levels of things you care about (In other words, do NOT use the same prefix you use for your root passwords and banking for forums access).  This also has the advantage that in your list (which you probably need to keep if you&#039;re requiring this advice) that you only need to store the suffixes.  So even if the list gets compromised it helps not unless that person also manages to obtain the prefix (which SHOULD NOT be written down anywhere - EVER).  The problem is there is always some wise crack somewhere that puts the prefix down as part of his list.

Also note that notebooks seem to have a nasty tendency of actually having RAM that keeps their content in relatively good condition for up to 10 minutes if properly prepped after shutting down.  This means that if someone steals a &quot;hot&quot; notebook, even if the screen is properly locked, they potentially can still get hold of the content on the drive by inserting a _very_ minimalistic CD with the appropriate tools on it to scan the RAM for the hard-drive key, then pull the power and the battery (no clean shutdown or some process may do the right thing and scrub the RAM), put the battery back and boot the LiveCD.

Also, your subnetting trick is security through obscurity unless none of the machines on your LAN segment knows how to route back through the buffalo.  Or it has a proper firewall only allowing connections through it that also goes over the ADSL router, in which case it&#039;s not particularly useful for &quot;extending the LAN&quot;.  Very nifty idea though, and definitely an advantage (most script kiddies - the type of person that would perform a non-targeted penetration - would not know how to detect this).

What I&#039;ve been saying for a while now is this:  We have the technology to enable computer security to a sufficient level, what we don&#039;t seem to have is the savvy to use it.</description>
		<content:encoded><![CDATA[<p>Regarding point 3 in the first list.  There are some routers that only supports WEP.  And yea, I even have a wireless card that cannot do 128-bit WEP, only 64-bit.  Go figure what these people were thinking considering that a decently fast machine could crack DES (A 56-bit encryption algorithm masquerading as 64-bit) in approximately an hour in 2004 already.  For every bit you add, the time theoretically doubles.</p>
<p>Regarding your practices, what helps for passwords, and if you must have lists, use a combination password.  In other words, have a prefix that is really hard to guess that you keep constant for all your machines, and then a suffix which is unique for each machine/purpose.  You should still decide who to trust with what and preferably have multiple prefixes for different levels of things you care about (In other words, do NOT use the same prefix you use for your root passwords and banking for forums access).  This also has the advantage that in your list (which you probably need to keep if you&#8217;re requiring this advice) that you only need to store the suffixes.  So even if the list gets compromised it helps not unless that person also manages to obtain the prefix (which SHOULD NOT be written down anywhere &#8211; EVER).  The problem is there is always some wise crack somewhere that puts the prefix down as part of his list.</p>
<p>Also note that notebooks seem to have a nasty tendency of actually having RAM that keeps their content in relatively good condition for up to 10 minutes if properly prepped after shutting down.  This means that if someone steals a &#8220;hot&#8221; notebook, even if the screen is properly locked, they potentially can still get hold of the content on the drive by inserting a _very_ minimalistic CD with the appropriate tools on it to scan the RAM for the hard-drive key, then pull the power and the battery (no clean shutdown or some process may do the right thing and scrub the RAM), put the battery back and boot the LiveCD.</p>
<p>Also, your subnetting trick is security through obscurity unless none of the machines on your LAN segment knows how to route back through the buffalo.  Or it has a proper firewall only allowing connections through it that also goes over the ADSL router, in which case it&#8217;s not particularly useful for &#8220;extending the LAN&#8221;.  Very nifty idea though, and definitely an advantage (most script kiddies &#8211; the type of person that would perform a non-targeted penetration &#8211; would not know how to detect this).</p>
<p>What I&#8217;ve been saying for a while now is this:  We have the technology to enable computer security to a sufficient level, what we don&#8217;t seem to have is the savvy to use it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

