<?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>E-Dribble &#187; hosting</title>
	<atom:link href="http://www.infosprite.com/tag/hosting/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.infosprite.com</link>
	<description>vaccuum packed mindless ramblings</description>
	<lastBuildDate>Tue, 17 Aug 2010 21:33:44 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>There&#8217;s one in the spotlight, he don&#8217;t look right to me&#8230;</title>
		<link>http://www.infosprite.com/2008/11/23/theres-one-in-the-spotlight-he-dont-look-right-to-me/</link>
		<comments>http://www.infosprite.com/2008/11/23/theres-one-in-the-spotlight-he-dont-look-right-to-me/#comments</comments>
		<pubDate>Sun, 23 Nov 2008 20:10:00 +0000</pubDate>
		<dc:creator>schwim</dc:creator>
				<category><![CDATA[Miscellaneous]]></category>
		<category><![CDATA[asshat]]></category>
		<category><![CDATA[hosting]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[vulnerability]]></category>

		<guid isPermaLink="false">http://www.infosprite.com/?p=220</guid>
		<description><![CDATA[I was forwarded a security notice by one of my competing webhosts(one of the few that I have yet to crush in my quest for world domination) concerning DaGoog.  Yes, it seems that there is another incredibly severe vulnerability, this time nefariously perpetrated by the same company that promised you that they would do no [...]]]></description>
			<content:encoded><![CDATA[<p>I was forwarded a security notice by one of my competing webhosts(one of the few that I have yet to crush in my quest for world domination) concerning DaGoog.  Yes, it seems that there is another incredibly severe vulnerability, this time nefariously perpetrated by the same company that promised you that they would do no evil.</p>
<p>Nah, I&#8217;m just kidding.  It&#8217;s just a bunch of blow-hard asshats that have found yet another scenario that will never actually happen to hear themselves talk.</p>
<p><span id="more-220"></span></p>
<p><a title="Everyone, run!" href="http://www.theregister.co.uk/2008/11/22/google_analytics_as_security_risk/" target="_blank">The Register</a>(UK based) wasted one more page on it than I will, allowing these devil&#8217;s advocate dipshits a platform to play what-if. I&#8217;ll give you the straight-up scoop, condensing the notice to a minimum length, while retaining the implications:</p>
<p>If Google wanted, they could use the javascript embedded for Analytics to do bad things on your site.</p>
<p>Left unsaid, but equally important are these notices:</p>
<p>1) If your webhost wanted, they could do bad things on your site.<br />
2) If your ISP wanted, they could do bad things on your site.<br />
3) If an employee with access wanted, they could do bad things on your site.<br />
4) If someone is looking over your shoulder when you access a restricted portion of your site, they will be able to do bad things on your site.<br />
5) If someone finds your password cheat-sheet, they will be able to do bad things on your site.</p>
<p>I could keep going, but no matter how hard I tried, I couldn&#8217;t come up with any more asinine possibilities than our quoted security experts have come up with.</p>
<p>It&#8217;s true.  If Google wanted to alter their code to introduce a malicious payload on a site using their analytics system, they could.  They could also hire ninjas to enter the NOC and steal your physical server.  They could also beat you up for your lunch money.</p>
<p>Dinis Cruz states “If I wanted a backdoor into the website, this would be one of the best ways to do it. It would allow somebody who knew about this to drop a payload in a way that almost wouldn’t be detected.“</p>
<p>For those that missed it, Dinis is proposing that the easiest way to compromise a site is to get a job at Google cleaning cubicles, work your way up to a position in which you have unmitigated control over the production code that Google uses and then alter it to access a restricted area on a site via a vulnerability you introduced.</p>
<p>An added bonus to this method is that you get to ride the Segways on the Google campus and have a certified organic vegan salad for free.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.infosprite.com/2008/11/23/theres-one-in-the-spotlight-he-dont-look-right-to-me/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
