[00:00.000 --> 00:14.180] Today, because I didn't see you checking into your office, and that every day around 10 a.m., you know, it's coffee break time, you'd like to go to your local Starbucks, give yourself a ha-pachino or something, and, boy, let's hope you'll log down to your VPN when you're left, [00:14.260 --> 00:17.080] because I'm going to sneak in and see whatever I want from your corporate network. [00:18.460 --> 00:22.160] Or, well, what if I just want something to steal from your laptop, be it corporate or personal? [00:22.960 --> 00:32.320] Well, thanks, you're sharing habits, I know, that you check in with open error bread every Saturday afternoon, that your co-depository for your personal project gets updated before you check in at home. [00:32.900 --> 00:34.820] You obviously must be using their network connection. [00:35.600 --> 00:38.300] What happens if I sit in that vanera and poison that Wi-Fi connection? [00:39.180 --> 00:42.960] Or just take your laptop when you're, you know, let's say refilling or emptying. [00:45.980 --> 00:52.140] A few other scenarios of, you know, why do you, an attractive co-worker, viewers go to dinner at the same fancy restaurant? [00:52.160 --> 00:53.360] Every Tuesday after work? [00:53.560 --> 00:55.120] Doesn't your spouse have yoga that night? [00:57.380 --> 01:00.300] Why are you in your coffee shop nowhere near your house every Friday night? [01:00.680 --> 01:03.140] Isn't that a little close to a local A&M meeting? [01:05.480 --> 01:06.640] But, wait, there's more. [01:07.800 --> 01:08.680] Stalking, obviously. [01:09.020 --> 01:10.580] I am an expert in that, I guess. [01:12.080 --> 01:15.100] Okay, someone might not be stalking you, because I'm boring. [01:15.440 --> 01:16.260] I'll admit it. [01:16.820 --> 01:18.140] But, what about my friends? [01:18.960 --> 01:20.720] Can I establish pattern of behavior? [01:20.720 --> 01:25.840] Can an attacker establish a pattern of behavior from the stuff that I post about my friends? [01:26.760 --> 01:28.120] Or surveillance in general? [01:28.300 --> 01:29.380] I mean, people love routines. [01:29.780 --> 01:30.720] Why did you break yours? [01:33.360 --> 01:35.260] So, let's talk about geotag. [01:35.380 --> 01:38.800] Now, EFF talked about a bunch of looks for threats to locational prices. [01:39.280 --> 01:42.920] Transit swipe cards, electronic tolling devices, easy pass, fast, whatever. [01:43.380 --> 01:47.000] Traffic cameras, mobile telephones, because I know no one here uses mobile telephones. [01:47.720 --> 01:51.660] Electronic swipe cards for doors, and then services telling you where your friends are. [01:51.820 --> 01:53.920] Like, foursquare, there was a couple more other ones. [01:54.160 --> 01:58.920] Like, four, foursquare, and I'll say, oh, your friends are nearby, because they checked in. [01:59.000 --> 02:00.300] But, it wasn't actually as much as public. [02:01.560 --> 02:05.120] However, they didn't miss one, and it's called geotags. [02:05.840 --> 02:09.060] Geotags are small bits of exit data. [02:09.160 --> 02:11.480] Next, that exit stands for a single image file format. [02:11.920 --> 02:16.680] And then it goes to latitude, longitude, altitude, and the relative direction of where that photo is taken. [02:17.200 --> 02:19.920] A lot of phones have this turned on by default. [02:20.660 --> 02:21.140] Why? [02:21.580 --> 02:23.340] Someone thought it was a good idea at some point. [02:24.920 --> 02:29.860] Already a bad idea, as for if you're taking photos for later publication. [02:29.860 --> 02:32.120] But, uh, what happens when you're doing something publishing? [02:34.880 --> 02:41.540] So, around, uh, February or so, Adam Savage from MythBusters decided to take a photo journal of his day. [02:42.160 --> 02:46.200] And she posts, started posting some photos of, hey, Gary, I'm getting breakfast. [02:46.360 --> 02:48.200] Here's the coffee I'm having again, I got a coffee cup. [02:48.480 --> 02:50.960] And he then posted, now it's off to work my niece. [02:51.120 --> 02:52.340] Wait, how'd that dog get in here? [02:52.420 --> 02:53.680] And he put her in a photo of Twin Vic. [02:54.520 --> 03:03.960] So, uh, one of my friends, Larry Hacks of Matrix, uh, who, uh, every week goes to, uh, does a podcast called Call of Automaturity Weekly, I highly recommend that you listen to it. [03:04.720 --> 03:14.260] Um, he decided, he did some work with EXIF data before with his, uh, sans gold paper, and he really likes EXIF, so he took the photo, downloaded it, and ran it through EXIF tool. [03:15.080 --> 03:18.400] Sorry, um, you have latitude and longitude on that, uh, photo there. [03:19.300 --> 03:19.740] Oops. [03:20.720 --> 03:25.220] And so, we decided to take that latitude and longitude, and run it through Google Maps. [03:28.960 --> 03:36.880] So, there's the map, and that's where he took that picture, and, um, Google decided to geocode us, and told us exactly where he lived. [03:37.920 --> 03:38.900] Uh, oops. [03:39.620 --> 03:45.420] And, if you, oh, sorry, so you pay very special attention to that photo of that house in the background, because it is a very unique house. [03:46.120 --> 03:50.060] And, if you look at Google Street View, and turn to the left, there's the house. [03:50.920 --> 03:53.800] So, we're obviously right around where he took that picture. [03:54.080 --> 03:55.280] Let's go look what's behind him. [03:55.720 --> 03:58.160] And, yep, that's a house there. [03:58.440 --> 04:00.060] And he says he parked in front of his house. [04:01.260 --> 04:02.560] Well, that's a nice house, Adam. [04:02.920 --> 04:07.640] Thank you, uh, Verbal, for taking that picture to us, because he walked in San Francisco and decided to go in front of, uh, Adam's house. [04:07.640 --> 04:10.100] Listen, Adam, I think you really need to trim some lawn. [04:10.640 --> 04:17.480] Uh, we did verify that this is his house, and if you actually go through public records, you can verify that. [04:17.600 --> 04:21.120] I'm sure Steve Rambom will talk all about, uh, that in his presentation. [04:21.620 --> 04:22.020] Alright. [04:22.500 --> 04:31.900] So, after this, uh, Johannes Rolwitz at the Sanis Institute, we don't know if it was coincidentally or if he's paying attention to Larry, uh, decided to follow this up with some more research on the Internet Storm Center blog. [04:31.900 --> 04:39.800] Uh, he wrote a script that reinforced TwitPic and analyzed over, uh, 15,000, uh, images from TwitPic. [04:40.140 --> 04:42.800] Over 10,000 had exit tags on it. [04:42.980 --> 04:45.920] Now, exit tags doesn't just, um, have all kinds of data on it. [04:46.040 --> 04:47.520] You know, was the flash fired for this one? [04:47.720 --> 04:48.220] Was it? [04:49.200 --> 04:50.640] What was the shutter speed? [04:51.340 --> 04:54.140] Photo stuff that I have no idea what the heck it was eating. [04:54.560 --> 04:57.200] But, um, over 10,000 had exit tags. [04:57.200 --> 05:02.660] Over 5,200, 5,297 had camera information. [05:02.840 --> 05:05.080] Which means this photo was taken with such and such a camera. [05:06.440 --> 05:08.000] 389 had GPS tags. [05:08.620 --> 05:10.420] About 2.5% of the total sample. [05:10.900 --> 05:13.340] Because I had to calculate that out because I wasn't a math major. [05:13.980 --> 05:21.860] Um, this may have been an incorrect calculation for the amount of, uh, photos that had exit tags because this script had a bug in it that I found. [05:22.560 --> 05:25.900] Uh, and it only was looking for certain, uh, image urinals. [05:26.200 --> 05:29.300] And the TwitPixer of the Society used two different types of urinals. [05:33.200 --> 05:36.400] Um, incidentally, we had no idea about this until about last week. [05:36.560 --> 05:44.900] There was a group of two guys, uh, Gerald Friedland and Robin Sommer from the International Computer Sciences Group of California who was also doing work on this. [05:45.060 --> 05:50.240] And they just released a paper called Cyber Casing the Joint on the privacy implications of geotag. [05:51.140 --> 05:57.000] Now, in cyber, anything with the word cyber is just a stupid term, but I will adopt this because they came up with a term for it. [05:57.700 --> 06:02.020] Uh, it was, uh, their, their, in their executive summary, rarely explains it anyway. [06:02.200 --> 06:13.840] While users typically realize that sharing locations has some implications to their privacy, we provide evidence that many are unaware of their full scope of the threat they face when doing so and often do not realize when they publish such information. [06:16.040 --> 06:27.760] So, we actually came to the same conclusion that they did, where people are doing this, they don't know that they're doing this, and they probably want to know that they are, so we decided to try something out with public awareness. [06:28.740 --> 06:35.780] Um, let's try to inform the people that, with what information people are really posting by taking a picture of their lunch every morning, or every afternoon. [06:37.360 --> 06:46.340] Um, the actually true outreacher, I thought it was a good idea to use Twitter, because that's where we saw all these people posting these photos in the first place. [06:46.760 --> 06:59.740] Uh, and there were enough bots out there, and we figured, if you say ponies, if you say zombies, if you say happy birthday to someone, if you say post them, along with many, many more, you get a nice little at reply saying, hey, someone so said this. [07:00.480 --> 07:09.420] And it's very interesting if you actually work with botnets, and you talk about zombies along, and you possibly get flagged by the zombie bot saying, oh, zombies are near Boston, Massachusetts, in my case. [07:09.840 --> 07:10.620] No, they're not. [07:13.140 --> 07:16.660] So we, uh, came up with our own bot called, I can stop you, because I can. [07:17.520 --> 07:33.080] And, um, we started crawling, uh, Twitter search results for, uh, for TwitPix, run it through, you know, see what the geotags are, hop it into Google Maps, and send them an app message to Lincoln, say, hey, someone is near, somewhere nearby this location. [07:34.360 --> 07:35.820] Initial outreach efforts were promising. [07:36.400 --> 07:38.080] We had people, you know, freaked out. [07:39.280 --> 07:42.420] We had people who had no idea how the heck we found out when we were talking about it. [07:42.880 --> 07:45.320] And we had some guy who asked us if we wanted to talk about it. [07:46.620 --> 07:49.340] He was at a hotel bar, and he said, hey, you're right here. [07:49.400 --> 07:50.540] And he said, yes, I am. [07:50.920 --> 07:52.800] Not a matter of fact, he wasn't, uh, in the meantime. [07:53.020 --> 07:54.800] We were probably going to join here, because we like beer. [07:55.700 --> 07:57.300] Um, we couldn't find out. [07:57.520 --> 08:01.460] And, um, we had a guy who replied to us, and I guess he deleted the tweet. [08:02.160 --> 08:06.700] Uh, and he basically, like, completely freaked out, saying, how are you? [08:06.780 --> 08:07.640] How do you know this? [08:07.960 --> 08:09.240] Blah, blah, blah, blah, blah. [08:09.520 --> 08:12.260] And I pictured this guy just, like, hiding under his desk. [08:12.380 --> 08:16.100] He has somebody knowing where he is, and the name is High Constructor. [08:20.320 --> 08:23.840] So, I set this up around, uh, 4:30 one day. [08:24.600 --> 08:26.500] End of the day, didn't have much on my back. [08:26.500 --> 08:32.160] The word control just, you know, fired off the script, put it as a, set it up as a daemon, and it just, you know, started firing off. [08:32.360 --> 08:33.900] Hey, I'm on a commute for two hours. [08:34.020 --> 08:35.820] Let's see what happens over those past two hours. [08:36.080 --> 08:36.920] I get home. [08:38.340 --> 08:38.980] That's funny. [08:39.420 --> 08:42.540] It's up, the script is running, but I'm not getting updates on my phone anymore. [08:42.780 --> 08:43.440] That's weird. [08:43.680 --> 08:43.980] Yeah. [08:44.680 --> 08:45.900] So, I'm logging into the account. [08:46.320 --> 08:47.800] Ooh, yeah. [08:48.060 --> 08:49.060] That, that wasn't good. [08:50.040 --> 08:59.860] So, um, I guess we tripped off, uh, I guess there is a spam bot, automatic spam filter, where if you add a lot of people, and you have a new account on Twitter, they suspend you. [09:00.380 --> 09:00.540] Whoops. [09:01.380 --> 09:04.440] Yeah, we, um, we actually have a drawing board on that one. [09:07.780 --> 09:13.620] So, we came up with ICanstalku.com, which is, we were originally going to do this, but heck, Twitter was already there. [09:13.800 --> 09:19.580] We could break the script in like five minutes, because now, a Twitter client is like the Hello World of computer programs. [09:20.280 --> 09:29.180] So, uh, we decided to go back for drawing board for a week, coded up this website, set it all up, which is instead of adding people, it just has this website of, hey, this person is at this location. [09:32.100 --> 09:34.940] So, I have it up here, and I didn't... [09:36.140 --> 09:37.560] I'm not typing the demo guys. [09:38.000 --> 09:45.020] So, this is what just before the, um, this is just before my talk started, around 11.55, and here are all the people that we see. [09:45.400 --> 09:48.420] The NRA blog, apparently, is somewhere near Oakton, Virginia. [09:49.580 --> 09:51.720] I wouldn't stop these people if I were you. [09:53.500 --> 09:55.300] I'm just saying it out there, you know. [09:56.220 --> 09:56.760] I'm all broke. [09:56.920 --> 09:59.520] Anyone can have guns if they want, but I'm just staying away from them. [10:00.020 --> 10:02.360] Um, just random people. [10:02.540 --> 10:03.120] You know, dog milk. [10:03.320 --> 10:04.160] That's an interesting name. [10:04.180 --> 10:07.680] Said cars, currently near 66 O'Farrell Street, San Francisco, California. [10:08.280 --> 10:11.320] Another interesting one that we found was a side-bobbing channel. [10:11.580 --> 10:16.020] Apparently, a lot of people like to use their iPhones to take photos and post stuff on their company Twitter account. [10:16.020 --> 10:19.120] You can see where their two locations are for their offices in L.A. [10:19.180 --> 10:22.080] and New York, if you, uh, read through one of our scripts, which I will tell you about later. [10:23.300 --> 10:24.220] Uh, just random people. [10:24.460 --> 10:27.600] So, I think it's a lot of random, because he was the only one ex-puff. [10:27.860 --> 10:27.920] Tough. [10:29.260 --> 10:30.180] Watch your head on that. [10:30.500 --> 10:34.680] He posted a photo, and he's currently near, uh, 1318 Marcus Creek, San Francisco, California. [10:35.040 --> 10:37.400] And if you load that into Google Maps... [10:40.450 --> 10:41.010] Oh, well. [10:41.610 --> 10:44.070] Um, if you load it into Google Maps, let's try to reload it. [10:44.490 --> 10:45.390] You can see if he understands. [10:45.630 --> 10:45.730] Yep. [10:45.730 --> 10:55.550] Um, it's actually, uh, the Google, uh, geocoding, and the, uh, service that we use, which is Geonames, they kind of are different to where exactly they think they are. [10:56.150 --> 11:00.250] But, uh, this is the, uh, more or less the exact location of where its GPS tag is. [11:00.830 --> 11:02.030] And here's the photo we showed. [11:02.750 --> 11:06.270] A photo of bacon gumballs, which I guess is a good idea. [11:06.410 --> 11:09.310] If you want to take, if you like bacon gumballs, take a photo of them posted up on Twitter. [11:09.310 --> 11:12.170] A lot of people like to post photos of their meals. [11:12.710 --> 11:13.630] I don't understand. [11:17.310 --> 11:24.950] So from here, um, like I said, I can map the location, I can view the tweet, and I would have done that if I wasn't on the, quite open network. [11:25.570 --> 11:28.330] Um, and I can actually reply to that. [11:28.330 --> 11:34.150] If you're logged into Twitter, and you click reply to that person, you can then, you know, send them a nice little message saying, Hey, I see you're right here. [11:34.250 --> 11:34.890] I can stop you. [11:35.590 --> 11:38.330] Um, this was basically, we set this up to get around to it. [11:38.770 --> 11:42.450] Rather than have to block at people, we decided to, you know, crowdsource it. [11:42.670 --> 11:45.830] Uh, and have other people do it. [11:45.910 --> 11:49.690] Basically, it's just me and my friends who find this highly amusing when people get freaked out. [11:54.130 --> 11:56.370] So, eventually, about a month later, Twitter relented. [11:56.370 --> 11:58.490] After completing our case, we had Twitter review our suspension. [11:58.850 --> 12:01.230] They were nice to us and said, Okay, just go do that. [12:03.090 --> 12:03.450] Alright. [12:04.110 --> 12:04.730] Thank you, Twitter. [12:05.290 --> 12:17.210] Uh, for a while, we just posted, uh, every hour or so, we decided, Hey, you know, we still, we still looked at that many links, we saw this many photos, we had x amount of errors, and we found x amount of information. [12:17.850 --> 12:20.190] Just something that we can do to make sure that the pod's still running. [12:20.930 --> 12:26.190] Uh, then, about two weeks ago, we decided, let's throw caution into the wind. [12:26.190 --> 12:28.350] Let's start adding people again, at a rate of one per hour. [12:30.650 --> 12:32.510] Of course, you can, let's look at this way. [12:32.570 --> 12:35.370] You can look at the pod, at twitter.com slash ikonsoft. [12:35.910 --> 12:36.690] That's all I'm saying. [12:36.830 --> 12:38.590] I'm not saying anything about getting recessed out. [12:39.090 --> 12:39.530] Okay. [12:40.330 --> 12:42.510] So, how, uh, how it works. [12:42.630 --> 12:45.470] A kernel script that we, uh, run, uh, searches for the URLs. [12:45.750 --> 12:57.150] There's a foot pic, it supports foot pic, it supports white frog, it supports movie pictures, and, uh, one of, uh, my cohorts decided to say, Hey, look at this photo called, listen to this photo service called sexy beacon. [12:58.370 --> 13:02.010] Um, twit pic, white frog, and movie pictures don't allow nudity. [13:02.010 --> 13:06.810] And so some enterprising, enterprising individuals said, Hey, let's go make a photo service for you. [13:07.090 --> 13:07.930] That was nudity. [13:11.850 --> 13:13.310] That's a bag, go for it. [13:14.410 --> 13:24.710] Um, so, they were, someone, he's obviously not married, he went through and, um, decided to code for us, and say, Hey, here's a code that will, that will work for this. [13:25.410 --> 13:36.630] Uh, and he actually, just about a month ago, we haven't actually included it yet, is there's another photo service, because you need two of these apparently, for the same service called twit sexy, same problem, even urban scrub exit data. [13:36.770 --> 13:44.470] So, you can find out if someone, posts a photo of themselves, uh, you can have, that they have geotag enabled on it. [13:44.950 --> 13:47.670] You can then say, Hey, I know exactly where they are. [13:48.330 --> 14:02.270] Also, once the picture of your other phone, they fed it into a Google app, and the Google app, uh, engine we used, is because they have slightly, uh, cheaper bandwidth, than my, uh, personal server, because we were quite literally, we'll go over that in a second, [14:02.650 --> 14:05.350] of how, uh, it takes a lot of bandwidth, to run this. [14:06.150 --> 14:09.070] Uh, the Google app then downloads a photo, and reads for exit data. [14:09.210 --> 14:22.810] The GPS tags are found, it's reverse geo-coded via the geo-name service, posted to the website, and, if it's time to post some statistics, about an hour after the application runs, every hour after it was posted some statistics, we drop the jocks on the latest users. [14:23.730 --> 14:26.950] It's completely random, it freaks people out, but that's what we're going for. [14:27.110 --> 14:31.690] GPS tags, if we don't find it with GPS tags, we're sad, and then we just move on to the next photo. [14:33.090 --> 14:37.210] Uh, from the website, you can say you can view the photo, map the location, and view the original screen. [14:38.050 --> 14:41.790] Uh, website users can also tell the person I know it, yeah, if you like it. [14:42.250 --> 14:42.770] I think you should. [14:44.270 --> 14:47.870] So, the trawler averages around 50 gigabytes of downloads per day. [14:48.170 --> 14:53.490] On average, about 35,000 tweets scanned, about 20,000 pictures, uh, downloaded. [14:54.270 --> 15:04.370] Uh, we're only looking for JPEGs, so people posted bitmapper, or GIF, or, one of the other, uh, one of the other types of photos that TwitPick, my product, supports, are not interested. [15:05.170 --> 15:10.050] Uh, we're only doing the very small portion of the photos uploaded to TwitPick. [15:10.150 --> 15:15.070] Initially, we decided, uh, we decided, uh, brute force URLs. [15:16.170 --> 15:18.630] Uh, we could average about 5 to 10 downloads per second. [15:18.830 --> 15:20.950] We couldn't keep up with the amount of photos being uploaded. [15:21.070 --> 15:23.750] We'd run it for about an hour, and we'd already be about 50 minutes behind. [15:24.290 --> 15:25.350] Uh, real-time. [15:27.690 --> 15:28.890] So, some privacy fail. [15:30.610 --> 15:32.130] This is a very nice, yeah, what do you do? [15:32.650 --> 15:33.650] He's chasing ducks. [15:33.870 --> 15:34.950] I'm sorry, he's chasing geese. [15:35.490 --> 15:37.810] Uh, although he knows that they bite, I found that out. [15:40.350 --> 15:41.910] So, this is great. [15:42.010 --> 15:43.050] Pay attention to the gazebo. [15:43.990 --> 15:44.850] On the left there. [15:45.590 --> 15:46.870] This is where the photo was taken. [15:47.010 --> 15:48.870] If you look at the left, there's gazebo. [15:48.870 --> 15:56.630] And, if we do some, uh, just look around, do some wiggling, we can find out where exactly the photos, the direction of the photos taken. [15:59.050 --> 16:00.050] Celebrities are not immune. [16:00.050 --> 16:05.870] We found out that Weird Aliekevich, uh, posts photos with geotags on the decided site. [16:06.050 --> 16:06.370] Hey! [16:06.710 --> 16:07.450] Fox and friends! [16:07.690 --> 16:08.810] Fox should sue these people. [16:09.190 --> 16:10.490] Well, apparently, we got things out. [16:11.830 --> 16:19.770] Uh, when we were Googling this address to see if this was actually his house, it was posted on more than a few websites, so it's public information. [16:19.930 --> 16:26.470] We didn't feel like we were really posting out something out there that, uh, people should know that Weird Aliekevich of this address a little bit. [16:27.750 --> 16:31.310] So, let's see how far we can take this. [16:31.490 --> 16:38.510] And, I was posting, I was going through, one of the original portions of the script decided to save all the pictures that we downloaded. [16:39.270 --> 16:42.690] And, we, we're just saving it, and we're looking through. [16:42.790 --> 16:48.190] I was looking through our mundane, iPad, lunch, dinner, kid, baby, my cat. [16:48.450 --> 16:48.810] Whoa! [16:49.590 --> 16:52.990] I'm not going to tell you what I saw, but, um, you can see what the cat saw. [16:59.590 --> 17:01.910] you just decided to post something to a picture. [17:02.130 --> 17:02.790] I don't know why. [17:05.230 --> 17:09.410] Unfortunately for Mr. X, he has, uh, geotags an alien. [17:10.910 --> 17:13.270] Phew, that's a very nice location right there. [17:14.030 --> 17:15.550] Whoops, what's that? [17:15.610 --> 17:20.010] Public records have that indicates that it's, uh, currently owned by, a William and a Jeanette. [17:20.530 --> 17:21.790] I wonder if that's William? [17:21.790 --> 17:23.130] So let's go find out. [17:24.790 --> 17:27.770] After we found William, we decided to start looking at this William person. [17:28.530 --> 17:29.910] And we couldn't find a Facebook for that name. [17:29.970 --> 17:30.810] No Twitter for that name. [17:30.930 --> 17:32.030] Google searches came up and empty. [17:32.550 --> 17:33.830] Well, where do we go from here? [17:34.130 --> 17:34.490] Hipple. [17:34.710 --> 17:35.670] Hipple was a great website. [17:36.210 --> 17:39.030] And we decided to start searching for a name. [17:39.810 --> 17:40.790] And we found it. [17:40.830 --> 17:41.530] It's on the bottom here. [17:41.650 --> 17:43.090] You obviously can't tell. [17:43.510 --> 17:44.590] We censored everything. [17:44.710 --> 17:46.770] Just quite frankly, they don't feel like dropping notes to those guys. [17:46.870 --> 17:47.430] It's a random guy. [17:47.590 --> 17:50.450] It's very unfortunate that he had a geotext name on his phone. [17:53.010 --> 17:56.510] So, I actually just found out about this website from this link. [17:56.650 --> 17:57.610] It's actually called Spokio. [17:57.730 --> 17:58.410] It's a very nice website. [17:59.050 --> 18:03.830] It says, you know, William here, he lives here with Brian and Jeanette. [18:03.930 --> 18:04.930] Why do you think he's with Brian? [18:06.830 --> 18:07.290] It's okay. [18:07.990 --> 18:10.390] William B, maybe you can find him. [18:12.050 --> 18:12.570] Whoops! [18:13.250 --> 18:14.270] There's a Facebook account. [18:14.970 --> 18:25.730] And it's important to realize that this guy posting these pictures of himself, there was no URL, there was no name, there was absolutely... this was a thoroughly anonymized account, as anonymous as you can get on Twitter. [18:27.450 --> 18:29.310] There were no links directly to him. [18:29.750 --> 18:31.850] So, just from view tags, we were able to find his Facebook. [18:32.110 --> 18:36.170] And from his Facebook... I did find kind of guilty, because he did say that he liked being a dad. [18:42.290 --> 18:43.770] I'm not repeating that. [18:46.570 --> 18:47.710] So, we caught his Facebook. [18:47.930 --> 18:49.550] So, dad caught his Facebook. [18:49.730 --> 18:57.870] On Facebook, we were able to find a birthday, his marriage status, didn't list a spouse, you can do the math, his friends, and two usernames. [18:58.390 --> 19:06.190] So, user name number one gives us, his Tumblr, his Flickr, his Flickr, and has a GPS.com account. [19:06.430 --> 19:09.110] Now, what is a GPS.com account, do you ask? [19:10.330 --> 19:10.770] Yeah! [19:11.030 --> 19:18.850] So, apparently, people thought it was a good idea to post... to load up GPS tracks of their day, or wherever. [19:19.670 --> 19:23.250] And he decided to post two, one of which was called Going Home. [19:23.470 --> 19:24.790] And that was the latest one. [19:24.830 --> 19:25.950] It was from a couple of years ago. [19:25.950 --> 19:29.610] And that looks awfully familiar. [19:31.530 --> 19:33.330] Yeah, that looks awfully familiar. [19:36.290 --> 19:38.730] So, we are pretty sure that this is the guy. [19:39.910 --> 19:44.110] Googling username number two gives us his Twitter account, which was linked to another Twitter account. [19:44.590 --> 19:58.230] Now, at this point, when I was actually looking for the original photos, because I wanted to see if we could match up the EXIF tags, to see if he was using the same phone, we went to his original anonymized account. [19:58.530 --> 19:59.330] It was deleted. [19:59.550 --> 20:04.330] However, the TwitVic account for that account was still there. [20:04.510 --> 20:07.290] So, TwitVic does not delete the photos after you delete your Twitter account. [20:07.470 --> 20:08.490] I was unaware of that. [20:11.470 --> 20:13.110] So, we took two of the photos. [20:13.430 --> 20:14.610] We compared the EXIF tags. [20:14.790 --> 20:15.750] The naked model wore a match. [20:15.850 --> 20:16.890] It was a BlackBerry 9000. [20:18.190 --> 20:19.450] Interested, like I said, in her saying. [20:19.610 --> 20:23.910] We also found his wife's Twitter account. [20:24.490 --> 20:25.050] All right. [20:26.510 --> 20:33.370] And so, this was around the time that we discovered this, and we were looking through his other Twitter account. [20:33.590 --> 20:35.430] He posted, and I'm an idiot, and I'm sorry. [20:37.230 --> 20:37.730] All right. [20:37.730 --> 20:37.830] All right. [20:38.310 --> 20:38.890] Let's see. [20:39.290 --> 20:45.370] Posting her to the pictures of himself online, then deleting that account, and apologizing on his other Twitter account. [20:45.470 --> 20:46.610] Let's go check on his wife's account. [20:47.770 --> 20:48.170] Yup. [20:48.410 --> 20:55.730] It appears that this is the person, because his wife's account decided to add the anonymous account, saying, you know, so-and-so has more secrets than I can ever address. [20:55.830 --> 20:57.790] I guess this wife thinks I'm always hiding stuff and something. [20:58.190 --> 20:59.590] Because he's hiding stuff. [21:00.830 --> 21:01.150] Oops. [21:04.210 --> 21:06.330] So, as always, you're Myles Mayberry. [21:06.450 --> 21:07.730] This is an extreme example. [21:08.090 --> 21:16.970] I guess, you know, deity, God, whoever you believe in, decided, you know, you saw Schwung, so I want to give you a nice little easy example for your presentation. [21:19.530 --> 21:22.790] I don't think many of you are posting images like that online. [21:23.010 --> 21:23.570] Some of you may. [21:23.690 --> 21:24.990] That's your bag, I'm not judging you. [21:26.490 --> 21:30.830] However, this is a good example of how many semi-anonymous accounts are there on Twitter. [21:30.970 --> 21:31.870] You know, you have a first name. [21:31.990 --> 21:32.730] You don't have a website. [21:33.150 --> 21:35.070] It's, you know, following by five people. [21:35.210 --> 21:36.270] It's following about ten. [21:37.730 --> 21:38.690] It's a random person. [21:38.810 --> 21:39.770] You don't know their real name. [21:39.850 --> 21:40.730] You don't know their website. [21:41.250 --> 21:42.770] However, they have geotags in it. [21:42.970 --> 21:45.910] If you want to know who that person is, you can probably find out. [21:47.030 --> 21:49.070] But they're all able to be tracked in the same manner. [21:51.050 --> 22:01.670] So, when we started adding people about two weeks ago, we noticed that we had a good, a slight majority of people were saying, geez, I did not know that I was posting this online. [22:02.750 --> 22:08.830] And the minority of people, they are evenly split between A, who the hell are you and how do you know this? [22:09.550 --> 22:12.230] And B, I know what a geotag is. [22:12.350 --> 22:13.250] I'm valuating the risk. [22:13.410 --> 22:17.330] I don't, you can't get much information from my feed because I self-censor myself. [22:17.970 --> 22:19.970] We completely support people doing this. [22:20.070 --> 22:23.350] The entire purpose of the website was just so people can make an informed decision. [22:24.230 --> 22:25.830] Hey, this is what we can find out from this. [22:25.950 --> 22:29.470] If you are okay, if you are comfortable with this, go for it. [22:31.590 --> 22:34.730] But we have suspicions that this was a lot worse than they thought. [22:34.830 --> 22:37.470] We could probably get a lot more information than they thought they were sharing. [22:38.010 --> 22:39.390] So, we decided to run an experiment. [22:39.570 --> 22:41.270] We heard about four people who were saying this to us. [22:41.270 --> 22:47.490] And we decided to plot their movements or geotag pics on a Google map. [22:49.230 --> 22:50.990] And it turns out we were right. [22:51.810 --> 22:52.850] So, it's very nice. [22:52.990 --> 22:55.210] It's actually a very pretty script that we released. [22:56.410 --> 23:00.270] Tested in a few years, we found the small bits of geotag information were pieces to a puzzle. [23:00.430 --> 23:04.410] Meaningless in and of themselves, but they make a very nice bigger picture. [23:05.310 --> 23:09.290] When you plotted it over time, if you saw a lot of... [23:09.290 --> 23:13.490] Over a very long period of time, a lot of geotag photos off a centralized location. [23:13.750 --> 23:16.030] It's pictures indoors, probably their house. [23:16.630 --> 23:20.190] Smaller clusters of an office, probably their workplace or a client. [23:21.010 --> 23:25.510] A smaller cluster of photos inside over a very small... [23:25.510 --> 23:29.410] Repeated times over a very small period of time. [23:29.410 --> 23:30.570] It might be a friend's house. [23:30.570 --> 23:32.670] Hey, you know, I'm going over to bubble your drinks. [23:32.870 --> 23:33.630] You're in a tab with scotch. [23:34.790 --> 23:35.450] Good for them. [23:36.490 --> 23:37.990] Also, other ones. [23:39.090 --> 23:42.210] So, we took four random users that were saying this to us. [23:42.410 --> 23:45.790] User A gets your hair cut at a certain regular spot and you like to take photos of it. [23:46.750 --> 23:52.230] User B attends his monthly local government meeting because he takes a photo of the minutes. [23:52.930 --> 23:54.110] User C has a cabin. [23:54.470 --> 23:59.190] You're able to see all these clusters of photos over a period of a week in the middle of nowhere, away from everything else. [23:59.310 --> 24:00.650] It must be a vacation spot. [24:02.790 --> 24:04.230] User B has a specific route. [24:04.390 --> 24:04.890] He bikes to work. [24:04.990 --> 24:07.550] He actually accidentally lost his bike chain one day. [24:07.890 --> 24:08.630] He had to go with it. [24:09.310 --> 24:12.130] He also likes to go to bars on Thursday night and he enjoys burgers. [24:14.250 --> 24:17.010] We posted a web log entry up on mehaniclabs.com. [24:17.110 --> 24:18.710] I'm going to give a link later in the photo. [24:19.610 --> 24:28.410] This was in response to a podcaster, not included in this experiment, who was concerned that he was posting... [24:29.310 --> 24:31.110] He wasn't concerned that he was posting this information. [24:31.350 --> 24:32.250] He called the spammers. [24:32.430 --> 24:35.190] He called us horrible, mean, nasty ugly things. [24:35.290 --> 24:36.810] And they're in it for the money, apparently. [24:39.430 --> 24:41.930] Apparently, these two other guys got a government grant. [24:42.070 --> 24:42.670] I wish I knew. [24:44.690 --> 24:45.690] But always keep... [24:45.690 --> 24:48.050] We can all sit here and say, this is stupid. [24:48.190 --> 24:50.210] But always keep in mind there are two sides to every discussion. [24:50.210 --> 24:53.070] You can feel to your right, but the other side feels the same exact way. [24:53.250 --> 24:55.670] And he was making the conscious decision that this was okay. [24:56.110 --> 24:56.510] Do. [24:56.770 --> 24:57.370] Go for it. [24:58.890 --> 25:00.090] So tools and data. [25:01.210 --> 25:02.210] This is what we've done. [25:02.370 --> 25:03.210] We've created a website. [25:03.470 --> 25:07.250] We've run a couple of small analysis on a couple of analysis on a couple of users. [25:07.530 --> 25:08.170] How about you? [25:08.330 --> 25:10.170] Why keep our data and tools bottled up on the server? [25:10.690 --> 25:11.350] That's boring. [25:11.790 --> 25:14.150] Why not open it up for everyone to cook at? [25:15.370 --> 25:17.130] So we're going to at least three things. [25:17.370 --> 25:18.070] Well, two things. [25:18.250 --> 25:19.210] Data and tools. [25:20.130 --> 25:27.650] We have a data set that contains latitude and latitude of over 65,000 photos posted to TwitPic, MyFront, BoothPicture, and SexyPeak. [25:28.070 --> 25:31.010] I probably have 90% of them are TwitPic, just so you guys know. [25:31.410 --> 25:32.730] So don't go searching for movies. [25:33.750 --> 25:34.590] If that's your thing. [25:37.490 --> 25:40.630] We scanned over 2.5 million URLs to get these photos. [25:41.610 --> 25:45.310] It stays in line with about that 3% Johannes came up with. [25:45.610 --> 25:47.910] Some days we see about 3.5. [25:47.910 --> 25:49.470] And I have other days we see 2.5. [25:49.570 --> 25:51.290] It usually covers right around 3%. [25:52.830 --> 25:58.210] We're not sure what you people can do with this, but I am sure that you young, enterprising you people will find something. [25:59.950 --> 26:01.470] We are also releasing tools. [26:01.890 --> 26:02.130] We are also releasing tools. [26:02.130 --> 26:02.750] Reaper and Stalker. [26:03.010 --> 26:04.050] Both written URLs. [26:04.730 --> 26:06.270] Python group developers. [26:08.210 --> 26:10.150] Some libraries are required. [26:10.670 --> 26:12.730] All of these are going to be available at mechaniclabs.com. [26:12.730 --> 26:16.010] As of tonight, I will not log into the website from this network. [26:20.470 --> 26:22.150] So, the first tool is called Reaper. [26:22.510 --> 26:26.370] It takes the URL from a photo service, extracts exit tags, and looks for geotags. [26:26.870 --> 26:31.950] The photo service supports TwitPic, Wi-Fi, MoviePicture, SexyPeak, and Flickr. [26:31.950 --> 26:32.630] Kind of. [26:32.710 --> 26:41.610] If you have one of those Twitter-enabled, what is it, F-L-I-C dot K-R URLs, it understands that you cannot look at them. [26:41.930 --> 26:42.510] We haven't... [26:42.510 --> 26:44.030] We just added that last week. [26:44.170 --> 26:45.070] We haven't actually taken... [26:46.190 --> 26:47.670] Looked at full URLs yet. [26:48.210 --> 26:50.770] Alternatively, what you can do is you can also double all the exit tags. [26:50.770 --> 26:51.370] So, it doesn't... [26:51.370 --> 26:53.030] If I call it, it doesn't have geotags. [26:53.210 --> 26:55.370] It's just that I can't find any geotags on it. [26:55.450 --> 26:58.770] But you can also look for photos... [26:59.770 --> 27:00.770] Make them on the cameras. [27:01.490 --> 27:07.030] If you really want to see how many photos have had the flash turned on on them for some reason, you could do that as well. [27:09.290 --> 27:15.510] So, stock.pl takes an entire user's photo screen and extract geotags from each photo. [27:16.350 --> 27:18.230] Currently, only scores TwitPic and Wi-Fi. [27:18.230 --> 27:22.990] It can output the location either to the console or to a TML file for Googler. [27:32.990 --> 27:37.370] No new information because I'm not tempting fate here. [27:41.340 --> 27:42.580] And this is... [27:42.580 --> 27:43.820] As you can tell, this is... [27:43.820 --> 27:46.240] Actually, I found a bug in stock. [27:46.240 --> 27:49.420] And stock.pl will be running out of six stats for it. [27:49.660 --> 27:50.800] As soon as you're home tonight. [27:51.160 --> 27:51.340] So... [27:51.340 --> 27:55.920] If you use stock.pl, you need to add to the top of... [27:55.920 --> 27:56.940] Use all the new key signals. [27:57.720 --> 27:59.680] I'm going to make sure that... [27:59.680 --> 28:00.560] That's what that is. [28:00.860 --> 28:02.640] So, we're going to use the... [28:02.640 --> 28:07.480] The 3.pl to use the photo that we saw earlier from XPTA. [28:07.480 --> 28:07.540] Okay. [28:13.130 --> 28:14.070] So, here it is. [28:14.210 --> 28:15.210] This is the latitude... [28:16.070 --> 28:16.490] Longitude... [28:16.490 --> 28:16.930] The... [28:18.590 --> 28:19.010] Latitude... [28:19.870 --> 28:20.290] Location... [28:20.290 --> 28:20.610] Of... [28:20.610 --> 28:21.130] Make is an Apple. [28:21.370 --> 28:23.490] And the model is an iPhone 3GS. [28:24.110 --> 28:25.430] Hasn't done an iPhone 4 yet. [28:30.790 --> 28:32.670] So, what we're also going to do is... [28:32.670 --> 28:33.810] I don't think this is that impressive. [28:33.970 --> 28:35.830] Because I think this is an only geotagged photo. [28:36.430 --> 28:36.610] But... [28:36.610 --> 28:38.330] We're going to run stock.pl on... [28:38.330 --> 28:38.590] You know... [28:38.590 --> 28:40.250] Username, XPTA, Service, Wi-Fi. [28:40.930 --> 28:43.430] End page means I'm only going to look at one page of photos. [28:43.630 --> 28:43.990] Because... [28:43.990 --> 28:45.770] We've seen people with like... [28:46.130 --> 28:47.250] 20 pages of photos. [28:47.470 --> 28:49.170] It takes an hour for this script to run. [28:53.650 --> 28:53.970] So... [28:53.970 --> 28:55.930] As you can tell, I'm grabbing each photo at C's. [28:55.950 --> 28:58.730] And the first one is the one that we just started. [29:06.380 --> 29:07.880] And of course, it's... [29:08.920 --> 29:09.840] It's slow or something. [29:09.980 --> 29:10.520] I didn't get a... [29:10.520 --> 29:11.540] It's probably... [29:15.960 --> 29:16.280] Alright. [29:16.580 --> 29:16.960] I'll tell you what. [29:17.020 --> 29:17.680] We'll go let this run. [29:17.700 --> 29:18.580] We'll come back to it later. [29:25.390 --> 29:25.710] So... [29:26.310 --> 29:27.750] Everyone comes up here and says... [29:27.750 --> 29:29.510] Everything you knew is probably now. [29:29.870 --> 29:30.190] Screwed. [29:30.230 --> 29:31.890] And then you ask them, well, how do we fix this? [29:31.890 --> 29:32.770] Well, I don't know. [29:34.010 --> 29:36.910] So we're actually going to provide a couple of 50,000 solutions for you. [29:38.170 --> 29:40.910] We saw there were three page places to eliminate the issue. [29:41.150 --> 29:43.350] Users, operating systems, and services. [29:44.270 --> 29:45.690] Users, it's what we're doing now. [29:45.830 --> 29:48.870] We're trying to inform users saying, Hey, this is bad. [29:49.030 --> 29:50.110] Look at what we can get from this. [29:50.230 --> 29:51.390] We want to learn how to disable it. [29:51.430 --> 29:52.270] Go check it out here. [29:53.050 --> 29:53.850] Yada, yada, yada. [29:54.710 --> 29:57.030] This is having a positive effect, but it's not so bad. [29:57.410 --> 29:58.050] The amount of... [29:58.050 --> 29:58.450] I mean... [29:58.450 --> 30:01.870] 1.6 million iPhones sold on the first day. [30:02.610 --> 30:06.370] Probably that about 90% of them have it enabled on them because... [30:06.370 --> 30:09.530] I want to take a photo of my iPad that I just bought as well. [30:10.070 --> 30:13.670] Do I want the location service enabled for this camera? [30:13.790 --> 30:14.950] Yeah, accept, accept, whatever. [30:15.290 --> 30:15.950] Hey, photo. [30:17.690 --> 30:19.110] Actually, I was unaware of this. [30:19.230 --> 30:24.210] So, if you had an original iPhone, it said, Would you like location services enabled for camera? [30:24.510 --> 30:25.590] You say, yes. [30:26.090 --> 30:33.130] If you keep on upgrading your iPhone to a 3G, to a 3GS, to a 4, it keeps that setting with it. [30:33.890 --> 30:38.610] So, even if you didn't have a GPS built into your original iPhone, you said location services. [30:38.830 --> 30:41.950] You know, I'm located within a couple of blocks from a cell tower. [30:42.150 --> 30:42.530] That's fine. [30:43.530 --> 30:47.370] If you didn't realize that that had changed between your... [30:47.370 --> 30:50.530] When you started getting a GPS, it's still enabled... [30:50.530 --> 30:50.970] You're still... [30:50.970 --> 30:52.890] You're now producing a lot more accurate information. [30:54.510 --> 30:54.930] Services. [30:55.910 --> 30:56.950] Scrub your exit data. [30:57.110 --> 30:58.510] Flickr does a pretty good job with this. [30:58.930 --> 30:59.490] You can... [30:59.490 --> 31:03.570] There's two settings on your account saying, Would you like to scrub exit tags? [31:03.830 --> 31:04.190] Yes. [31:04.390 --> 31:06.130] Or, would you like exit tags, public viewable? [31:06.250 --> 31:06.470] No. [31:06.930 --> 31:10.030] Would you like to have your GPS data, public viewable? [31:10.190 --> 31:10.490] No. [31:11.250 --> 31:11.530] Great. [31:12.030 --> 31:17.130] However, every time I submit a photo to Flickr, Flickr can then see exactly where I am. [31:17.690 --> 31:20.050] When Flickr has that photo, they can do whatever they want. [31:20.230 --> 31:23.130] Right on the upload process, they can say, Hey, look for geotags. [31:23.290 --> 31:24.490] That here's an acquisition. [31:24.790 --> 31:26.630] We can then send them whatever we want. [31:26.730 --> 31:27.310] We now know that. [31:28.910 --> 31:29.610] Operating systems. [31:29.810 --> 31:30.830] This is the best. [31:30.990 --> 31:33.650] Make a geotagging opt-in, which technically it is now. [31:33.730 --> 31:38.510] However, with a lot of phones it says, Would you like to enable geotagging for this? [31:38.730 --> 31:39.110] Yes. [31:39.950 --> 31:40.730] Okay, that's it. [31:40.810 --> 31:41.970] That is now your default setting. [31:42.110 --> 31:43.550] Would you like to enable geotagging for this? [31:43.670 --> 31:43.950] No. [31:44.330 --> 31:44.510] Okay. [31:45.350 --> 31:46.370] Next time you take food. [31:46.470 --> 31:47.650] Would you like to enable geotagging? [31:47.810 --> 31:48.130] No. [31:48.610 --> 31:50.390] It just keeps on asking you. [31:50.390 --> 31:54.150] You don't like the way to turn it off permanently unless you start going in settings, which actually is the same. [31:54.350 --> 31:56.650] You can subscribe on microstock.com. [31:57.890 --> 32:00.930] The two researchers came up with an excellent idea. [32:01.290 --> 32:07.870] And they actually created a mock-up in their report saying, Would you like to enable geotagging for this photo? [32:08.010 --> 32:08.190] Yes. [32:08.190 --> 32:10.230] How accurate would you like it to be? [32:10.350 --> 32:16.210] And they said, you know, latitude and longitude within a block, within a mile, within, you know, within the same state. [32:16.410 --> 32:18.050] And then it will randomize the positioning. [32:18.530 --> 32:19.750] This was a really good idea. [32:19.930 --> 32:23.110] I guess this is why they had a government grant for that one little mock-up. [32:26.070 --> 32:28.810] So, in closing, be careful what you share. [32:30.210 --> 32:31.810] Think about how it can be used. [32:32.450 --> 32:45.830] When I started looking at it, or really started thinking about it, when I took photos that aren't geotagged, when I took photos, no, I'm fine with that information possibly coming from me. [32:45.950 --> 32:49.670] However, what about those people that I'm taking a photo of, or photos that are in the background? [32:50.730 --> 32:52.530] At least, what am I taking a photo of? [32:52.650 --> 32:54.650] Am I taking a photo of a MakerBot at a friend's house? [32:54.750 --> 32:56.570] Which we saw a photo of when it was geotagged. [32:56.650 --> 32:58.270] I mean, I don't know that MakerBot is sitting in that. [32:59.090 --> 32:59.950] We could have that. [33:04.210 --> 33:06.990] Make sure geotagging is off on your phone, naturally. [33:07.870 --> 33:10.330] And don't use GPS.com unless you want to install it. [33:10.450 --> 33:12.350] I don't see why people would want to use it. [33:12.450 --> 33:24.610] Someone suggested to me that if you're like a biker or a runner, and you want to have paths, running paths uploaded to your friends, that would be a good use for it, just to make sure it doesn't lead to your house. [33:27.650 --> 33:28.010] Shoutouts. [33:28.170 --> 33:29.110] Larry, Hats of the Matrix. [33:29.110 --> 33:30.790] He did a lot of round work. [33:30.950 --> 33:36.530] He did a lot of stuff with exit tags for his SANS, GOLDS, I think it was the GCIH paper. [33:37.030 --> 33:39.330] And he answered a lot of my stupid exit questions. [33:39.870 --> 33:41.750] Every week, Paul.com Security Weekly. [33:41.910 --> 33:44.150] He's on there with a group of other very smart individuals. [33:44.350 --> 33:45.590] It's a lot of fun to listen to. [33:45.850 --> 33:47.110] Paul.com.com. [33:48.930 --> 33:50.770] Sellout ponies in the rest of the hammock labs. [33:51.370 --> 33:53.670] Especially for being incredibly good voting. [33:53.830 --> 33:55.690] If you wanted me to say this, I don't know. [33:55.850 --> 33:56.730] Ladies, he's on the market. [34:00.310 --> 34:04.430] Fervil was the nice one that actually went out to Adam's house and took a photo of him. [34:06.210 --> 34:07.810] So, I guess we'll have questions for this. [34:07.890 --> 34:08.830] Well, actually, four new questions. [34:08.970 --> 34:10.010] Let's go see if the script's done right. [34:12.950 --> 34:13.590] Boston 2600. [34:13.970 --> 34:14.970] I don't go there anymore. [34:14.990 --> 34:15.310] Sorry. [34:15.850 --> 34:16.850] I moved out of the area. [34:17.450 --> 34:19.430] So, anyway, this person has three photos. [34:19.430 --> 34:20.810] I'm sorry. [34:20.970 --> 34:21.390] Two photos. [34:21.950 --> 34:22.570] I'm sorry. [34:22.570 --> 34:22.590] Two photos. [34:22.590 --> 34:23.310] Wide Broad Street. [34:23.490 --> 34:30.130] The near 1318 Market Street San Francisco and San Felipe United States. [34:30.470 --> 34:36.210] When GeoNames doesn't get a street address, we then go to a place name. [34:36.570 --> 34:42.090] Which we haven't really found out how they've made this place name possible. [34:42.090 --> 34:45.870] Like, we'll get like, you know, this random town name, United States. [34:46.050 --> 34:48.030] And if we Google it, it'll say, oh yeah, it's in New Jersey. [34:51.030 --> 34:53.770] But, it's for, it's vague, but it works. [34:54.150 --> 34:57.990] However, if we probably wrote that last two months, we'll tell us exactly where it is. [34:58.150 --> 35:00.530] Let's go do that, because we still have plenty of time. [35:27.470 --> 35:27.970] There we go. [35:28.030 --> 35:28.870] Hollister, California. [35:35.620 --> 35:40.720] And I'd also show you a photo, but I've had bad experiences with that, as you've seen. [35:41.000 --> 35:43.040] So, I'm not going to post that up there with the public. [35:44.600 --> 35:47.100] So, you can turn off your legs so I can see who I'm talking to. [35:47.100 --> 35:48.160] We'll have to take questions. [36:00.180 --> 36:00.760] Yeah. [36:01.060 --> 36:01.400] Hi. [36:03.540 --> 36:05.060] I was, uh... [36:05.660 --> 36:07.460] You're probably familiar on that. [36:07.680 --> 36:09.720] If you have an iPhone, it's Apple products. [36:09.940 --> 36:11.880] They have a new feature called Places. [36:12.300 --> 36:18.920] That takes your photos in the public library and geotypes, new geotypes and maps them out. [36:18.920 --> 36:20.100] Uh-huh. [36:22.600 --> 36:33.280] Recently, I was traveling internationally, and I had my iPhone with me, but I had airplane mode turned on, because I can buy a package in the country. [36:33.580 --> 36:40.400] So, I assume there is absolutely no, uh, no signal running on my phone. [36:40.680 --> 36:48.320] But when I got back, I noticed that all of my pictures were geopagged and mapped, and I was wondering if you know how to deal with that. [36:48.320 --> 36:50.420] Well, probably because they don't turn the GPS on. [36:50.520 --> 36:51.800] GPS is receive only. [36:52.000 --> 36:54.360] And I don't know, is this an iPhone 4 or an iPhone 3? [36:55.320 --> 36:55.800] So, yeah. [36:55.900 --> 37:00.440] I thought iPhone 3 was only, um, assisted GPS where it depends on cell phone towers. [37:00.440 --> 37:02.480] But, I could be wrong. [37:02.840 --> 37:07.020] Our previous research suggested that if you have airplane mode on, it doesn't geotag photos. [37:07.300 --> 37:09.380] So, um, I guess we can research it. [37:10.260 --> 37:16.940] Um, if you go to, I can stalk you, there's a way of going, and it's, uh, how, it's a link we're on the top. [37:21.090 --> 37:22.150] Hang on, that signal. [37:29.420 --> 37:29.820] Oh. [37:33.040 --> 37:34.880] Okay, so I guess we're on fire right now. [37:35.360 --> 37:40.460] Um, mehemiclabs.com, that's where everything is. [37:40.800 --> 37:42.220] Um, shows that by data set.