{"id":742,"date":"2009-02-06T18:19:50","date_gmt":"2009-02-07T02:19:50","guid":{"rendered":"http:\/\/cubist.cs.washington.edu\/Security\/?p=742"},"modified":"2009-02-06T18:19:50","modified_gmt":"2009-02-07T02:19:50","slug":"current-event-google-releases-%e2%80%98latitude%e2%80%99","status":"publish","type":"post","link":"https:\/\/secblog.cs.washington.edu\/Security\/2009\/02\/06\/current-event-google-releases-%e2%80%98latitude%e2%80%99\/","title":{"rendered":"Current Event: Google Releases \u2018Latitude\u2019"},"content":{"rendered":"<p>Google has released a new product called \u2018Latitude\u2019. It is an extension based on the extremely popular Google Maps web application that allows users to track the exact location of friends and family members using the GPS signal in their mobile phones. This product has already launched, and even with the received criticism Google is standing behind its new product.<\/p>\n<p><!--more--><\/p>\n<p>This release has opened a whole new world of privacy concerns. The system works by allowing users to download an application on their mobile device that reports their location back to Google servers. Friends and family can then use \u2018Latitude\u2019 to get real-time information about where a person is. A user does have to download the application to their cell phone to participate, but any adversary would only need to gain physical access to the device for a couple of minutes to install the application unbeknownst to the cell phone owner. This vulnerability presents itself to stalkers, prying employees, jealous partners, and obsessive friends, to name a few.<\/p>\n<p>For a company who\u2019s motto is \u201cDon\u2019t Be Evil\u201d, this seems a little contradictory. It\u2019s easy to envision this product wreaking havoc in people\u2019s lives, especially when you consider the scenarios mentioned above. Google has taken some precautions, but London based Privacy-International does not feel they go far enough. The only acceptable solution in their opinion is to have the application regularly prompt the user that the service is turned on. This would be very annoying; the application does indicate when it is on, but it may not be obvious to many people.<\/p>\n<p>Another major concern that comes to mind is a distributed attack. With cell phones becoming more powerful and completely ubiquitous, they are vulnerable to a widespread attack. If an attacker created a virus that massively subscribed users, a serious state of panic could ensue during the time in which every person\u2019s real-time location was available online.<\/p>\n<p>Personally, I don\u2019t think this service should have been launched in its current state. I can see the fun and benefit in this application, but it is just too easy to subvert right now. This is a clear example of the moral conflict when it comes to technology vs. privacy. One of the main concerns in this debate is always of falling down a slippery slope, and this seems like it could be the start of one. I think this will certainly stir up controversy, and we will have to wait and see how the public and the media respond. If there are security breaches with this service, it will only take a few of them before public opinion turns against a technology like this.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Google has released a new product called \u2018Latitude\u2019. It is an extension based on the extremely popular Google Maps web application that allows users to track the exact location of friends and family members using the GPS signal in their &hellip; <a href=\"https:\/\/secblog.cs.washington.edu\/Security\/2009\/02\/06\/current-event-google-releases-%e2%80%98latitude%e2%80%99\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":75,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4,7],"tags":[],"class_list":["post-742","post","type-post","status-publish","format-standard","hentry","category-current-events","category-ethics"],"_links":{"self":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/742","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/users\/75"}],"replies":[{"embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/comments?post=742"}],"version-history":[{"count":3,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/742\/revisions"}],"predecessor-version":[{"id":745,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/posts\/742\/revisions\/745"}],"wp:attachment":[{"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/media?parent=742"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/categories?post=742"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/secblog.cs.washington.edu\/Security\/wp-json\/wp\/v2\/tags?post=742"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}