Monday, April 29, 2013

Cybercasing the Joint: Privacy Implications of Geotagging

Note: While reading the article on Geotagging at Wikipedia I found at "Subnote 12"  the following interesting PDF: study. Since it didn't print right here you can view the whole thing at: atic.usenix.org/events/hotsec10/tech/full_papers/Friedland.pdf

2nd note: It makes the point that it is not only personal privacy and bodily harm that is a problem with Geotagging. It also makes the point that geotagging could actually be used to wage organized war against areas, groups or individuals and is even a more severe national security threat for all nations from this point of view.



Cybercasing the Joint: On the Privacy Implications of Geo-T
agging
Gerald Friedland
1
Robin Sommer
1
,
2
1
International Computer Science Institute
2
Lawrence Berkeley National Laboratory
Abstract
This article aims to raise awareness of a rapidly emerging
privacy threat that we term
cybercasing
: using geo-tagged in-
formation available online to mount real-world attacks. Wh
ile
users typically realize that sharing locations has some imp
lica-
tions for their privacy, we provide evidence that many
(i)
are
unaware of the full scope of the threat they face when doing
so, and
(ii)
often do not even realize
when
they publish such
information. The threat is elevated by recent developments
that make systematic search for specific geo-located data an
d
inference from multiple sources easier than ever before. In
this paper, we summarize the state of geo-tagging; estimate
the
amount of geo-information available on several major sites
, in-
cluding YouTube, Twitter, and Craigslist; and examine its p
ro-
grammatic accessibility through public APIs. We then prese
nt
a set of scenarios demonstrating how easy it is to correlate g
eo-
tagged data with corresponding publicly-available inform
ation
for compromising a victim’s privacy. We were, e.g., able to fi
nd
private addresses of celebrities as well as the origins of ot
her-
wise anonymized Craigslist postings. We argue that the secu
-
rity and privacy community needs to shape the further devel-
opment of geo-location technology for better protecting us
ers
from such consequences.
1 Introduction
Location-based services are rapidly gaining traction in
the online world. With big players such as Google and
Yahoo! already heavily invested in the space, it is not
surprising that GPS and WIFI triangulation are becom-
ing standard functionality for mobile devices: starting
with Apple’s iPhone, all the major smartphone makers
are now offering models allowing instantaneously upload
of
geo-tagged
photos, videos, and even text messages to
sites such as Flickr, YouTube, and Twitter. Likewise, nu-
merous start-ups are basing their business models on the
expectation that users will install applications on their
mobile devices continuously reporting their current loca-
tion to company servers.
Clearly, many users realize that sharing location infor-
mation has implications for their privacy, and thus de-
vice makers and online services typically offer different
levels of protection for controlling whether, and some-
times with whom, one wants to share this knowledge.
Sites like
pleaserobme.com
(see
§
2) have started cam-
paigns to raise the awareness of privacy issues caused
by intentionally publishing location data. Often, how-
ever, users do not even
realize
that their files contain lo-
cation information. For example, Apple’s iPhone 3G em-
beds high-precision geo-coordinates with all photos and
videos taken with the internal camera unless explicitly
switched off in the global settings. Their accuracy even
exceeds that of GPS as the device determines its position
in combination with cell-tower triangulation. It thus reg-
ularly reaches resolutions of +/- 1 m in good conditions
and even indoors it often has postal-address accuracy.
More crucial, however, is to realize that publishing
geo-location (knowingly or not) is only
one
part of the
problem. The threat is elevated to a new level by the
combination
of three related recent developments:
(i)
the
sheer amount of images and videos online that make even
a small relative percentage of location data sufficient for
mounting systematic privacy attacks;
(ii)
the availability
of large-scale easy-to-use
location-based search
capabil-
ities, enabling everyone to sift through large volumes of
geo-tagged data without much effort; and
(iii)
the avail-
ability of so many
other
location-based services and an-
notated maps, including Google’s Street View, allow-
ing correlation of findings across diverse independent
sources.
In this article, we present several scenarios demon-
strating the surprising power of combining publicly
available geo-information resources for what we term
cy-
bercasing
: using online tools to check out details, make
inferences from related data, and speculate about a lo-
cation in the real world for questionable purposes. The
primary objective of this paper is to raise our commu-
nity’s awareness as to the scope of the problem at a time
when we still have an opportunity to shape further de-
velopment. While geo-tagging clearly has the potential
for enabling a new generation of highly useful personal-
ized services, we deem it crucial to discuss an appropri-
ate trade-off between the benefits that location-awareness
offers and the protection of everybody’s privacy.
We structure our discussion as follows. We begin
with briefly reviewing geo-location technology and re-
lated work in
§
2. In
§
3 we examine the degree to which
1

we already find geo-tagged data “in the wild”. In
§
4 we
demonstrate the privacy implications of combining geo-
tags with other services using a set of example cybercas-
ing scenarios. We discuss preliminary thoughts on miti-
gating privacy implications in
§
5 and conclude in
§
6.
2 Geo-Tagging Today
We begin our discussion with an overview of geo-
tagging’s technological background, along with related
work in locational privacy.
Geo-location Services
. An extensive and rapidly
growing set of online services is collecting, providing,
and analyzing geo-information. Besides the major play-
ers, there are many smaller start-ups in the space as well.
Foursquare, for example, encourages its users to con-
stantly “check-in” their current position, which they then
propagate on to friends; Yowza!! provides an iPhone ap-
plication that automatically locates discount coupons for
stores in the user’s current geographical area; and Sim-
pleGeo aims at being a one-stop aggregator for location
data, making it particularly easy for others to find and
combine information from different sources.
In a parallel development, a growing number of sites
now provide public APIs for structured access to their
content, and many of these already come with geo-
location functionality. Flickr, YouTube, and Twitter all
allow queries for results originating at a certain location
.
Many third-parties provide services on top of these APIs.
PicFog, for example, provides real-time location-based
search of images posted on Twitter. Such APIs have also
already been used for research purposes, in particular for
automated content analysis such as work by Crandall et
al. [2], who crawled Flickr for automatically identifying
landmarks.
Locational Privacy
. Location-based services take
different approaches to privacy. While it is common to
provide users with a choice of privacy settings, the set of
options as well as their defaults tend to differ. YouTube,
for example, uses geo-information from uploaded videos
per default, while Flickr requires explicit opt-in. Like-
wise, defaults differ across devices: Apple’s iPhone geo-
tags all photos/videos taken with the internal camera un-
less specifically disabled; with Android-based phones,
the user needs to turn that functionality on.
The privacy implications of recording locations have
seen attention particularly in the blogosphere. However,
these discussions are mostly anecdotal and rarely con-
sider how the ease of searching and correlating infor-
mation elevates the risk. From a more general perspec-
tive, the EFF published a thoughtful white-paper on
Lo-
cational Privacy
[3], discussing implications of secretly
recording peoples’ activity in public spaces.
Pleaserobme.com
[9] was probably the first ef-
fort that demonstrated the malicious potential of sys-
tematic location-based search: the authors leveraged
Foursquare’s “check-ins” to identify users who are cur-
rently not at their homes. However, in this case loca-
tions were deliberately provided by the potential victims,
rather than being implicitly attached to files they upload.
Also, geo-tagging is a hazard to a much wider audience,
as even people who consciously opt-out of reporting any
information might still see their location become public
through a third party publishing photos or videos, e.g.,
from a private party. Besmer and Lipford [1] examine a
related risk in the context of social networks that allow
users to add identifying tags to photos published on their
profile pages. The authors conduct a user study that re-
veals concerns about being involuntarily tagged on pho-
tos outside of a user’s own control. They also present a
tool for negotiating photo sharing permissions.
To mitigate the privacy implications, researchers
have started to apply privacy-preserving approaches
from the cryptographic community to geo-information.
Zhong et al. [4] present protocols for securely learning
a friend’s position if and only if that person is actually
nearby, and without any service provider needing to be
aware of the users’ locations. Olumofin et al. [7] discuss
a technique that allows a user to retrieve point-of-interes
t
information from a database server without needing to
disclose the exact location. Poolsappasit et al. [8] presen
t
a system for location-based services that allows specifi-
cation and enforcement of specific privacy preferences.
From a different perspective, Krumm [5] offers a survey
of ways that computation can be used to both protect and
compromise geometrical location data.
GPS and WIFI Triangulation
. Currently, it is mostly
high-end cameras that either come with GPS functional-
ity or allow separate GPS receivers to be inserted into
their Flash connector or the so-called “hot shoe”. Like-
wise, it is mostly the high-end smartphones today that
have GPS built in, including the iPhone, Android-based
devices, and the newer Nokia N-series. An alternative
(or additional) method for determining the current lo-
cation is WIFI access point or cell-tower triangulation:
correlating signal strengths with known locations allows
a user or service to compute a device’s coordinates with
high precision, as we demonstrate in
§
4. If a device
does not directly geo-tag media itself, such information
can also be added in post-processing, either by correlat-
ing recorded timestamps with a corresponding log from
a hand-held GPS receiver; or manually using a map or
mapping software.
Metadata
. For our discussion, we are primarily con-
cerned with
geo-tagging
, i.e., the process of adding lo-
cation information to documents later uploaded online.
The main motivation for geo-tagging is the personalized
organizing and searching that it enables. For example,
by including current location and time with a series of
vacation photos, it becomes easy to later group them au-
2

tomatically, as well as to find further photos online from
others who visited the same place.
The most common mechanism for associating loca-
tions with photos are
EXIF
records, which were orig-
inally introduced by the Japan Electronic Industry De-
velopment Association for attaching metadata to images
such as exposure time and color space. Since then EXIF
has been extended to also cover geographical coordinates
in the form of latitude and longitude. Currently, EXIF is
used only with JPEG and TIFF image files and WAV au-
dio files. However, most other multimedia formats can
contain metadata as well, often including geo-tags. For
videos, proprietary “maker notes” are the most common
form for storing locations. All these formats are easy
to parse with the help of standard tools and libraries, in-
cluding browser plugins for revealing metadata as well as
Apple’s
Preview
program that offers a convenient
Locate
button for geo-tags taking one directly to Google Maps.
In general, metadata can pose a privacy risk by storing
unexpected information not immediately apparent when
opening a document. Murdoch and Dornseif [6] demon-
strated that editing software may leave thumbnails of the
original image behind in EXIF data, and similar prob-
lems have been found with other formats, such as Word
and PDF documents.
It turns out, however, that many automatic image ma-
nipulation tools—especially those used in content man-
agement systems—“accidentally” discard metadata dur-
ing processing. For that reason, we find that images on
many of the larger Web sites do
not
have any metadata
attached. As we discuss in
§
4, we did however find EXIF
data (and thus also locations) on private homepages and
blogs as well as on sites such as Craigslist and TwitPic.
3 Prevalence of Geo-Tagged Data
In this section a number of experiments are presented that
aim at understanding to what degree image and video
data is geo-tagged today.
Flickr
. Flickr has comprehensively integrated geo-
location into its infrastructure and it provides a powerful
API for localized queries. This API allows direct queries
on the number of images that are, or are not, geo-tagged
within a certain time interval. Examining all 158 mil-
lion images uploaded in the first four months of 2010,
we found that about 4.3% are geo-tagged. When looking
at the development over past years, we see—somewhat
counter-intuitively—a declining trend: while there was
steep increase in geo-tagging from 2004 to about the end
of 2006 (when it peaked at 9.3%), its share has been de-
clining to the current level since then. We speculate that
Flickr’s opt-in privacy policy is the reason for this devel-
opment: as more users are joining Flickr, the number of
those explicitly enabling EXIF import is likely shrinking,
and thus the number of images not geo-tagged is rising
much more quickly than those that do. This would then
indicate that such an opt-in policy is indeed suitable to
contain the amount of geo-tagging.
We also examined the brands of cameras used for
taking the photos that have geo-information, derived
from their EXIF records which can be retrieved via
Flickr’s API as well. Doing so however requires one
API request per image, and hence we resorted to ran-
domly sampling a 5% set of all geo-tagged images up-
loaded in 2010. We found that the top-five brands were
Canon (31%), Nikon (20%), Apple (6%), Sony (6%),
and Panasonic (5%). A closer look at the individual mod-
els confirms our observation in
§
2 that today it is mostly
devices at the higher end of the price scale that are geo-
tagging.
YouTube
. Like Flickr, YouTube also allows queries
restricted to specific locations. With YouTube however,
due to restrictions of its API, it is not possible to di-
rectly determine the number of geo-tagged videos, as we
can with Flickr. YouTube restricts the maximum num-
ber of responses per query to 1,000; and while it also
returns an (estimated) number of total results, that fig-
ure is also capped at 1,000,000. Still, we believe we can
estimate the share of geo-tagged videos in the follow-
ing way: We first submitted a number of different un-
constrained queries that each yielded a set of 1,000,000
results. We then refined these queries by adding an addi-
tional filter to include only videos that had geo-location.
We found that the sizes of the remaining result sets range
from about 30,000 to 33,000 videos. In other words, out
of what we assume to be a random sample of 1,000,000
YouTube videos, roughly 3 % have geo-location. While
this number is clearly an estimate, it matches with what
we derived for Flickr.
1
Craigslist
. The virtual flea market Craigslist allows
users to include photos with their postings by either up-
loading them directly to the company’s servers, or by in-
serting external HTML
IMG
links. In the former case,
images are recoded and stripped off their metadata. In the
latter case, however, such a link can point to the original
image as taken by the poster’s camera and thus may still
have its EXIF records intact. To estimate the number of
geo-tagged photos linked to from Craigslist postings, we
examined all postings to the San Franscisco Bay Area’s
For Sale
section over a period of four days (including a
weekend). While Craigslist does not provide a dedicated
query API, it offers RSS feeds that include the postings’
full content. Consequently, during our measurement in-
terval, we queried a suitably customized RSS feed every
10 minutes for the most recent 500 postings having im-
ages, each time downloading all linked JPEGs that we
had not yet seen. In total, we collected 68,729 images,
1
YouTube’s API distinguishes between videos
without
location,
with
coarse
location (usually manually added, e.g. “Berlin”), and with
exact
location. For our experiments, we only considered the latte
r.
3

# Model
# Model
414 iPhone 3G
6 Canon PowerShot SD780
287 iPhone 3GS
3 MB200
98 iPhone
2 LG LOTUS
32 Droid
2 HERO200
26 SGH-T929
2 BlackBerry 9530
20 Nexus One
1 RAPH800
9 SPH-M900
1 N96
9 RDC-i700
1 DMC-ZS7
6 T-Mobile G1
1 BlackBerry 9630
Table 1:
Devices geo-tagging photos found on Craigslist
.
of which about 48% had EXIF information. 914 images
were tagged with GPS coordinates, i.e., about 1.3% of
the total. We presume that this number is lower than what
we found for Flickr and YouTube because many photos
on Craigslist are edited before posting. Still, already wit
h
a cursory look we found several cases where precise lo-
cations had the potential to compromise privacy, as we
discuss in
§
4. We also examined the camera models used
to take the geo-tagged Craigslist photos (Table 1). While
the iPhone models are clearly ahead of all other models,
it is interesting to see a wide range of other devices.
4 Cybercasing Scenarios
In this section we take the perspective of a potential at-
tacker to investigate examples of
cybercasing
. We fo-
cus on four different scenarios: one on Craigslist, one on
Twitter, and two on YouTube. To not further harm the
privacy of the persons involved in our experiments, we
refrain from describing identifying specifics.
Craigslist
. In our first scenario, we manually in-
spected a random sample of Craigslist postings contain-
ing geo-located images, collected as described in
§
3.
One typical situation we found was a car being offered
for sale with images showing it parked in a private park-
ing space. Most of the time it was straight-forward for us
to verify a photo’s geo-location by comparing the image
with what we saw on Google Street View.
A fair number of postings with geo-located images
also offered other high-valued goods, such as diamonds,
obviously photographed at home, making them potential
targets for burglars. In addition, many offered specifics
about when and how the owner wants to be contacted
(“please call Sunday after 3pm”), enabling speculation
about when somebody might not be at home. Since many
postings published more than one image, and some loca-
tions were the origin of more than one offer, a more ac-
curate estimation of the postal address would have been
possible through averaging the geo-tags.
While we did not further verify addresses, we set
up an experiment to assess GPS accuracy in a typical
Craigslist setting: We first photographed a bike in front
of a garage with an iPhone 3G, as if we wanted to offer
it for sale (see Figure 1). When we then entered the geo-
coordinates that the phone embedded into the picture into
Street View, Google was able to locate the photo’s posi-
tion within
+
/
1
m
. Such accuracy is much higher than
what we believe most people would expect.
Among the Craigslist postings with geo-information
we also found a significant number where the poster
chose to not specify a home address, phone number,
or e-mail account and opted for Craigslist’s anonymous
emailing option. We take this as an indication that many
posters were not aware that their images were geo-tagged
and thus leaked their location information.
We note that while we only performed experiments
with Craigslist’s “For Sale” category, it is not hard
to imagine what consequences unintended geo-tagging
might have in “Personals” or “Adult Services”.
Twitter
. Blogging has become a common tool for
celebrities to provide their fans with updates on their
lives, and most of such blogs contain images. Likewise,
many celebrities now also use public Twitter feeds that,
besides potentially being geo-tagged themselves, may
also link to external images they took. Our second sce-
nario therefore involved tracking a popular reality-TV
host who is very active on Twitter. His show is broad-
cast on US national television and has been exported into
various foreign countries. In recent episodes, the chan-
nel even began advertising that the host is maintaining a
Twitter feed. It turns out that most images posted to that
feed—including photos taken at the host’s studio, places
where he walks his dog, and of his home—were taken
with an iPhone 3GS and are hosted on
TwitPic
, which
conserves EXIF data. In addition, we noticed that the
host is also commonly tweeting while he is traveling or
meeting other well-known people away from home. Us-
ing the Firefox plug-in
Exif Viewer
, a right-click on any
of the Twitter images suffices to reveal these locations
using an Internet map service of one’s choice. Again, av-
eraging geo-tags from multiple images taken at the same
location would increase accuracy further.
Geo-location can also be exploited for taking the op-
posite route: finding a celebrity’s
non
-advertised Twit-
ter feed intended only for private purposes (e.g., for ex-
changing messages with their personal friends
2
). Doing
so becomes possible with sites such as
Picfog
, which al-
lows anybody to search all images appearing on Twit-
ter by keyword and geo-location in real-time. Hav-
ing a rough idea of where a person lives thus allows a
user to tailor queries accordingly until the right photo
shows up. As an experiment, we succeeded in finding a
non-advertised but publicly-accessible Twitter-feed of a
celebrity with a residence in Beverly Hills, CA.
YouTube
. In our final setup, we examined whether
one can semi-automatically identify the home addresses
of people who normally live in a certain area but are cur-
rently on vacation. Such knowledge offers opportunities
2
By default, Tweets are public and do not require authenticat
ion.
4

Figure 1:
Photo of a bike taken with an iPhone 3G and a corresponding Goo
gle Street View image based on the stored geo-
coordinates. The accuracy of the camera location (marked) i
n front of the garage is about
+
/
1
m
. Many classified advertisements
come with photos of objects offered for sale, with geo-tags a
utomatically added.
for burglars to break into their unoccupied homes. We
wrote a script using the YouTube API that, given a home
location, a radius, and a keyword, finds a set of matching
videos. For all the videos found, the script then gath-
ers the associated YouTube user names and downloads
all videos that are a certain
vacation distance
away and
have been uploaded the same week.
In our first experiment, we set the home location to be
in Berkeley, CA, downtown and the radius to 60 miles.
As the keyword to search for we picked “kids” since
many people publish home videos of their children. The
vacation distance was 1000 miles. Our script reported
1000 hits (the maximum number) for the initial set of
videos matching “kids”. These then expanded to about
50,000 total videos in the second step, identifying all
other videos from the corresponding users. 106 of these
turned out to have been taken more than 1000 miles away
and uploaded the same week. Sifting quickly through
the titles of these videos, we found about a dozen that
looked promising for successful cybercasing. Examin-
ing only one of them more carefully, we already had a
hit: a video uploaded by a user who was currently travel-
ing in the Caribbean, as could clearly be seen by content,
geo-tagging, and the date displayed in the video (one day
before our search). The title of the video was similar to
“first day on the beach”. Also, comments posted along
with the video on YouTube indicated that the user had
posted multiple vacation videos and is usually timely in
doing so. When he is not on vacation, he seemed to
live with his kids near Albany, CA (close to Berkeley)
as several videos were posted from his home, with the
kids playing. Although the geo-location of each of the
videos could not be pinpointed to a single house due to
GPS inaccuracies indoors, the user had posted his real
name in the YouTube profile, which would likely make it
easy to find the exact location using social engineering.
We also performed a second search with the same pa-
rameters, except for the keyword which we now set to
“home”. This time, we found a person who seemed to
have moved out of the city. While many of that person’s
videos had been geo-tagged with coordinates at a specific
address in San Francisco, the most recent video was at a
place in New Jersey for which Google Maps offered a
real-estate ad including a price of $ 399,999. The person
had specified age and real name in his YouTube entry.
Finally, we note that using our 204-line Python script we
were able to gather all the data for these two experiments
within about 15 minutes each.
5 Improving Locational Privacy
Educating users about its misuse potential is clearly key
to avoid wide-spread misuse of location information.
However, it is our experience that currently, even many
tech-savvy users find it difficult to accurately assess the
risk they face. We thus believe that the security and pri-
vacy community needs to take a more active role in shap-
ing the deployment of this rapidly emerging technology.
We deem it crucial to ensure that users
(i)
are put into
a position where they can make informed decisions; and
(ii)
are sufficiently protected unless they explicitly opt-in
to potentially risky exposure. In the following, we frame
preliminary suggestions towards this end.
On a general level, we encourage our community to
aim for a consensus on what constitutes an acceptable
privacy policy for location-based services. Current ap-
proaches differ widely across devices and services, and
we believe that establishing a unified strategy across
providers would go a long way towards avoiding user
confusion and thus unnecessary exposure. More specif-
ically, we believe that a global opt-out approach to shar-
ing high accuracy location-information is almost always
inappropriate. Rather, users should need to acknowl-
edge usage at least on a per-application basis. Apple’s
iPhone 3G takes a step into the right direction by re-
5

Figure 2:
Our mockup of a mobile-phone dialog to give users
more control over the geo-location embedded in their photos
.
questing permission each time a new application wants
to access the GPS sensor. However, its user interface
still has two short-comings:
(i)
it does not apply that pol-
icy to photos/videos taken with the internal camera; and
(ii)
for each application, it is an all-or-nothing decision.
Regarding the latter, it seems that often simply reducing
a location’s resolution might already be a suitable trade-
off. As an experiment on how such an approach could be
supported, Figure 2 shows a mockup we did for extend-
ing the iPhone’s standard permission dialog with a slider
allowing to choose an acceptable resolution for each ap-
plication in intuitive terms. According to the choice, the
device would then strip off a corresponding number of
the least-significant digits of any coordinates. Not only
would this give users more control, but it would also ex-
plicitly point out that house-level accuracy is in the cards
.
For jail-broken iPhones, there are already 3rd-party tools
available that spoof the location information visible to
other applications.
An alternative approach is enforcing privacy policies
at the time when files are uploaded to public reposito-
ries, rather than when they are captured/recorded. For
example, a browser could provide the user with a dialog
similar to our iPhone mockup when she is about to send
videos to YouTube. The browser would then adapt any
geotags according to the user’s choice before proceeding.
It is also stimulating to think about how APIs such as
those offered by Flickr and YouTube can offer a higher
level of privacy without restricting geo-technology in
its capabilities. One way would be for
them
to re-
duce the resolution; that however would limit some ser-
vices significantly. Conceptually more interesting is to
leverage approaches from related fields such as privacy-
preserving data mining. As discussed
§
2, researchers
have started to examine such approaches, yet we are
not aware of any real-world API that incorporates these
ideas.
6 Final Remarks
This article makes a case for the emerging privacy issue
caused by wide-spread adaptation of location-enabled
photo and video capturing devices, allowing potential at-
tackers to easily “case out joints” in cyberspace. Several
factors aggravate the problem. First, many people are
either unaware of the fact that photos and videos taken
with their cell phones contain geo-location, especially
with such accuracy; or what consequences publishing the
information may have. Second, even experts often fail
to appreciate the easy search capabilities of today’s on-
line APIs and the resulting inference possibilities. Third
,
the fact that only a small percentage of all data is cur-
rently geo-tagged must not mislead us into ignoring the
problem because
(i)
with all the commercial pressure, the
number seems poised to rise; and
(ii)
our preliminary ex-
periments demonstrate that even a seemingly small frac-
tion like 1% can already translate into several hundred
relevant cases within only a small geographical area.
Finally, we want to emphasize that we are not ad-
vocating avoiding the use of geo-location in general or
geo-tagging specifically. It is a wonderful technology
that drives innovation in many areas. However, we feel
there is a clear need for education, as well as for research
on designing systems to be location-aware while at the
same time offering maximum protection against privacy
infringement.
Acknowledgments
We would like to thank Gregor Maier and
Nicholas Weaver for discussions and feedback, the anonymou
s
reviewers for valuable suggestions, and Michael Ellsworth
for
English corrections. This work was supported in part by NSF
Award CNS-0831779 and by NGA NURI #HM11582-10-1-
0008. Opinions, findings, and conclusions or recommendatio
ns
are those of the authors and do not necessarily reflect the vie
ws
of the supporters.
References
[1] Andrew Besmer and Heather Richter Lipford. Moving Beyon
d
Untagging: Photo Privacy in a Tagged World. In
Proc. Interna-
tional Conference on Human factors in Computing Systems
, 2010.
[2] David Crandall, Lars Backstrom, Dan Huttenlocher, and J
on
Kleinberg. Mapping the Worlds PhotosMapping the Worlds Pho
-
tos. In
Proc. World Wide Web Conference
, 2009.
[3] EFF. On Locational Privacy, and How to Avoid Losing it For
ever.
http://www.eff.org/wp/locational-privacy
.
[4] Ian Goldberg Ge Zhong and Urs Hengartner. Louis, Lester a
nd
Pierre: Three Protocols for Location Privacy. In
Proc. Privacy
Enhancing Technologies Symposium
, 2007.
[5] John Krumm. A Survey of Computational Location Privacy.
Per-
sonal and Ubiquitous Computing
, 13(6):391–399, 2009.
[6] Steven J. Murdoch and Maximillian Dornseif. Far More
Than You Ever Wanted To Tell Hidden Data in Internet.
http://md.hudora.de/presentations/forensics/
HiddenData-21c3.pdf
.
[7] Femi Olumofin, Piotr K. Tysowski, Ian Goldberg, and Urs He
n-
gartner. Achieving Efficient Query Privacy for Location Bas
ed
Services. In
Proc. Privacy Enhancing Technologies
, 2010.
[8] Nayot Poolsappasit and Indrakshi Ray. Towards Achievin
g Per-
sonalized Privacy for Location-Based Services.
Transactions on
Data Privacy
, 2(1):77–99, 2009.
[9] Please Rob Me - Raising Awareness About Over-sharing.
http://pleaserobme.com
end quote from:
atic.usenix.org/events/hotsec10/tech/full_papers/Friedland.pdf

No comments: