HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
hubert3
iSniff-GPS
Python2013–2013
hubert3 / iSniff-GPS

iSniff-GPS

Passive sniffing tool for capturing and visualising WiFi location data disclosed by iOS devices

2Distinct people
2Mentions
0Explicit recommenders
1.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Passive sniffing tool for capturing and visualising WiFi location data disclosed by iOS devices

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2013-05-11 14:32:26 UTC to 2013-07-16 00:01:53 UTC. Weeks start Monday, UTC.

012013-05-06 00:00:00 UTC to 2013-05-13 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 62013-05-13 00:00:00 UTC to 2013-05-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-20 00:00:00 UTC to 2013-05-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-05-27 00:00:00 UTC to 2013-06-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-03 00:00:00 UTC to 2013-06-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-10 00:00:00 UTC to 2013-06-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJun 102013-06-17 00:00:00 UTC to 2013-06-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-06-24 00:00:00 UTC to 2013-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-01 00:00:00 UTC to 2013-07-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-08 00:00:00 UTC to 2013-07-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-07-15 00:00:00 UTC to 2013-07-22 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 15

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
May 62013-05-06 00:00:00 UTC2013-05-13 00:00:00 UTC110
May 132013-05-13 00:00:00 UTC2013-05-20 00:00:00 UTC000
May 202013-05-20 00:00:00 UTC2013-05-27 00:00:00 UTC000
May 272013-05-27 00:00:00 UTC2013-06-03 00:00:00 UTC000
Jun 32013-06-03 00:00:00 UTC2013-06-10 00:00:00 UTC000
Jun 102013-06-10 00:00:00 UTC2013-06-17 00:00:00 UTC000
Jun 172013-06-17 00:00:00 UTC2013-06-24 00:00:00 UTC000
Jun 242013-06-24 00:00:00 UTC2013-07-01 00:00:00 UTC000
Jul 12013-07-01 00:00:00 UTC2013-07-08 00:00:00 UTC000
Jul 82013-07-08 00:00:00 UTC2013-07-15 00:00:00 UTC000
Jul 152013-07-15 00:00:00 UTC2013-07-22 00:00:00 UTC101

What Hacker News says

2 sources
Yeah, but he whole "pervasive surveillance" thing means there's no meatspace equivalent of Perfect Forward Security here. It only takes _one_ instance where someone can map my MAC address to an identity for the entire recorded chain to lose it's anonymity - one venue "in the system" where I make a credit card purchase or divulge my identity. Hell - if we're being paranoid, a sufficiently determined wifi access point operator has a _lot_ at their disposal to attempt to de-anonymise a specific phone. iOS for example under some conditions transmits the MAC addresses of the last 3 access points its connected to. There's a reasonably high chance on of them's my home and/or work wifi - use some tool that'll sniff all those ARP requests and geolocate them[1] to get partial address data. A determined enough attacker might be snooping any traffic
Read the rest
that the phone puts through the network. Using non SSL protected POP3 or IMAP - guess who's got your email address (and password!)? Does your Twitter/InstaGram/Pintrest/4Square/SnapChat/whatever client always use SSL? Are ay of them vulnerable to sslstrip or MITM-able with unsigned certs? How many websites does your phone browser happily send unencrypted cookies to that're capable of providing strong hints to your identity? (Even HN did this up to a few months ago. "superuser2" doesn't reveal much about you, but knowing I'm "bigiain" in HN is enough to uniquely identify me.) Now you've got me wondering just how many of the widespread free wifi rollouts are relying on this as part of their monetisation. McDonalds free wifi would be a great network to do this on. My local shopping center free wifi is almost certainly run by the same company as all of the othe AMP Capital shopping centers in Australia. And now that I think about it, they're pushing the center wifi hard, with things like Pinterest promotions and "like us on Facebook" and "download our iPhone app" - all things that could easily deanonymise my MAC address... [1] https://github.com/hubert3/iSniff-GPS
In Attention, Shoppers: Store Is Tracking Your Cell

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.