<?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>Angels of security &#187; google</title>
	<atom:link href="http://angelsofsecurity.com/blog/tag/google/feed/" rel="self" type="application/rss+xml" />
	<link>http://angelsofsecurity.com/blog</link>
	<description>Musings of an infosec renegade</description>
	<lastBuildDate>Tue, 02 Aug 2011 19:01:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>IPV6 + MAC addresses + Geolocation = Privacy fail</title>
		<link>http://angelsofsecurity.com/blog/2010/10/29/ipv6-mac-addresses-geolocation-privacy-fail/</link>
		<comments>http://angelsofsecurity.com/blog/2010/10/29/ipv6-mac-addresses-geolocation-privacy-fail/#comments</comments>
		<pubDate>Fri, 29 Oct 2010 20:08:02 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[application security]]></category>
		<category><![CDATA[geolocation]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[ipv6]]></category>
		<category><![CDATA[privacy]]></category>

		<guid isPermaLink="false">http://angelsofsecurity.com/blog/?p=683</guid>
		<description><![CDATA[Update: You can probably scratch this whole idea &#8211; see the comments for details. First, a little background on geolocation for those who haven&#8217;t heard of this before: Google has been collecting wifi data while doing streetview. One of the things they collect is MAC addresses of wireless networks. Google, using the above MAC addresses [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Update</strong>: You can probably scratch this whole idea &#8211; see the comments for details.</p>
<p>First, a little background on geolocation for those who haven&#8217;t heard of this before:</p>
<ol>
<li>Google has been collecting wifi data while doing streetview. One of the things they collect is MAC addresses of wireless networks.</li>
<li>Google, using the above MAC addresses and GPS data, is now offering a <a href="http://code.google.com/apis/gears/api_geolocation.html">geolocation</a> service. You just send in the MAC addresses of any wireless networks in range, and Google will helpfully tell you where you are.</li>
<li>While a browser is supposed to prompt a user before sending the MAC addresses off to Google, it is certainly possible for anyone to submit any MAC address they know of to Google. Sam Kamkar has a <a href="http://samy.pl/mapxss/">proof of concept</a> for this.</li>
</ol>
<p>The summary of the above is this: If you have a MAC address, google will tell you where it has seen that MAC address.</p>
<p>Now for the kicker. <a href="http://en.wikipedia.org/wiki/IPv6_address">IPV6 autoconfig</a>, by default, loads the mac address into the last 64 bits of the IP address. (Not directly &#8211; technically the bytes FFFE are added to the middle, and 1 bit is flipped, but this is all easily reversed. Suffice it to say obtaining a MAC address from this sort of IP address is trivial). See where this is going yet? If you want to know where an IPv6 address is located in the real world, just traceroute to the device, pull the MAC address from the device immediately prior to your target, and see if Google has a record of it. If your target is behind NAT, you can skip even this simple step. This attack is probably mostly theoretical right now since the vast majority of wireless networks are still IPv4, but if IPv6 ever does take off, this will become a real worry.</p>
<p>Credit where credit is due: I got this idea while watching the video of Samy Kamkar&#8217;s presentation entitled &#8220;<a href="http://vimeo.com/15492594">How I met your girlfriend</a>&#8220;. Samy goes from end to end, showing how to get a person&#8217;s real life location. He only talks about IPv4, so for the last steps he convinces the target to click a link, exploits their home router, and pulls the MAC address from there using the default credentials. I basically take this attack and consider it in the IPv6 world, where none of the technical wizardry is necessary and the attack difficulty is significantly lower.</p>
]]></content:encoded>
			<wfw:commentRss>http://angelsofsecurity.com/blog/2010/10/29/ipv6-mac-addresses-geolocation-privacy-fail/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		</item>
		<item>
		<title>new web app scanner</title>
		<link>http://angelsofsecurity.com/blog/2010/03/22/new-web-app-scanner/</link>
		<comments>http://angelsofsecurity.com/blog/2010/03/22/new-web-app-scanner/#comments</comments>
		<pubDate>Mon, 22 Mar 2010 16:30:48 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[application security]]></category>
		<category><![CDATA[software]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[skipfish]]></category>

		<guid isPermaLink="false">http://angelsofsecurity.com/blog/?p=566</guid>
		<description><![CDATA[A friend of mine dropped me a note to point out that Google has released an open source web application security scanner called skipfish. I haven&#8217;t used it yet (installing as I type), and will hopefully have some thought on it soon.]]></description>
			<content:encoded><![CDATA[<p>A friend of mine dropped me a note to point out that Google has released an open source web application security scanner called <a href="http://code.google.com/p/skipfish/">skipfish</a>. I haven&#8217;t used it yet (installing as I type), and will hopefully have some thought on it soon.</p>
]]></content:encoded>
			<wfw:commentRss>http://angelsofsecurity.com/blog/2010/03/22/new-web-app-scanner/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>captcha on demand</title>
		<link>http://angelsofsecurity.com/blog/2009/06/29/captcha-on-demand/</link>
		<comments>http://angelsofsecurity.com/blog/2009/06/29/captcha-on-demand/#comments</comments>
		<pubDate>Mon, 29 Jun 2009 18:42:08 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Security Architecture and Design]]></category>
		<category><![CDATA[captcha]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[Michael Jackson]]></category>

		<guid isPermaLink="false">http://angelsofsecurity.com/blog/2009/06/29/captcha-on-demand/</guid>
		<description><![CDATA[With the death of Michael Jackson last week, Google saw an unprecedented level of Michael Jackson related searches. The most impressive thing about Google&#8217;s response is that they apparently deploy captcha tests on demand only when they think there is an automated attack going on. As someone who hates having to type in those letters [...]]]></description>
			<content:encoded><![CDATA[<p>With the death of Michael Jackson last week, Google saw an <a href="http://googleblog.blogspot.com/2009/06/outpouring-of-searches-for-late-michael.html">unprecedented level</a> of Michael Jackson related searches. The most impressive thing about Google&#8217;s response is that they apparently deploy captcha tests on demand <a href="http://lh3.ggpht.com/_Ffh95I6Kep4/SkUg5wOKkRI/AAAAAAAACU8/l0ayIfDo-fs/s912/3660499057_f36b4b59a3_o.png">only when they think there is an automated attack</a> going on. As someone who hates having to type in those letters printing in the most unreadable manner possible, I think this is a great step up.</p>
]]></content:encoded>
			<wfw:commentRss>http://angelsofsecurity.com/blog/2009/06/29/captcha-on-demand/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

