1,170 karma · joined April 24, 2010
If this post manages to stay on the front page, they may get enough traction, but still unlikely
each shot is defined by one unique hash and a geo location.. waiting to see a tweet about "hit" or perhaps "miss" but those wouldnt need to be ACKed
17 73 f2 7b a0 00 00 00
23 115 242 123 160 00 00 00
Each client has his/her own UUID(the tweet) and the geolocation is where the client is located.
It seems as though the googuns_staging was the trial, all fake/useless location and googun_prod(as the name suggests) is the actual "in-the-wild" run of locating all of its clients
Also interesting is at the moment there are many tweets ending in either a350000000 or baf200000000 but that may just be coincidence based on some counter thats incrementing
<meta name="keywords" content="googun googun googun googun googun googun googun googun gay gay gay gay gay gay gay gay seattle seattle seattle seattle hot hot hot hot hot hot hot hot hot Tshirts t shirt t shirt t shirt t shirt t-shirt t-shirt t-shirt coffee coffee coffee coffee coffee">
see: https://twitter.com/googuns_staging/status/22294385659595980...
https://maps.google.com/maps?q=-20.73906235%2C-145.82847672&...
EDIT: I wonder if it does some sort of transform on the number to get an IP addr? perhaps its part of a IPv6 Addr?
Perhaps its a distributed brute-force on a password or checksum being carried out by a botnet? Its interesting distributed this is, too bad we dont have IP addrs associated with the posts
http://www.ted.com/talks/leslie_t_chang_the_voices_of_china_...
At least that was the state of things about 2 weeks ago
Ive done some benchmarks testing Intel Atom processors Atom330's and D525's against Tegra3 processors. On average the Terga3 processors outperformed the Atoms 4x-8x in Flop/s per Watt.
Admittedly that is not the only important metric, but gives an initial performance comparison between ARM and x86 performance
my fairly complex alphanumeric+symbol password IS in the dump, though not prepended truncated with 0's and the other one I found, which my coworker admitted was too short and alpha only, was in the dump with prepended 0's.
This could validate the fact that the truncated hashes are actually already cracked.
ScreenCap: http://i.imgur.com/oeNai.png