81–90 of 184 posts
The post is speculation; perhaps s/does/might/ or s/does/could/ in the title.
The title is a question. Which is why it ends with a questionmark. The article attempts to answer the question with theories. The article isn't written by Joe Random; it is written by Matthew Green who teaches cryptography at John Hopkins university.
Earlier quoted context omitted.
Also interested. Could you describe the process?
Sure. I pulled my data in the standard takeout.google.com/ process. The result is a json (? iirc). I parsed the json into x, y, and rasterized it using gdal. https://imgur.com/a/ZhyTsDV See I wasn't sure if I lost it in the couch in the living room, the office, or the bedroom. This got me within a few feet.
By my data, do you mean data from Google Android Device Configuration Service?
If you're logged into Chrome or GSuite tools from desktop locations, I just wonder how useful the data from those other products would be, if it even has location data.
I'm downloading my data archive to check it out...
Can this be used as essentially 100% effective anti-theft? If an Apple device is constantly emitting a BLE beacon code that can't effectively be changed in any way by a thief... ...then unless a thief keeps the device in their basement and never has anybody visit, your stolen device will almost certainly be detected sooner or later, and then you just call the police? Even if the thief has sold it by that point and di…
Total aside, but kinda relevant. I lost my phone like a dufus about a two weeks ago. Battery died and I had no idea where it was. When I pulled the my google location history, it was too coarse to tell me anything other than 'at your house'. However, I was able to pull the raw data from google and post process it by time stamp into a series of rasters that were fine enough for me to see that the phone was definitely…
Can this be used as essentially 100% effective anti-theft? If an Apple device is constantly emitting a BLE beacon code that can't effectively be changed in any way by a thief... ...then unless a thief keeps the device in their basement and never has anybody visit, your stolen device will almost certainly be detected sooner or later, and then you just call the police? Even if the thief has sold it by that point and di…
I would assume that a factory reset would take care of it. Otherwise you couldn't sell the phone to someone else and revoke your ability to find it.
Earlier quoted context omitted.
I would assume that a factory reset would take care of it. Otherwise you couldn't sell the phone to someone else and revoke your ability to find it.
You can’t do a factory reset without the device password.
As with anything public + blockchain it had all the Cryptoeconomics incentives problems you would expect and I never solved them.
Finding a lost device has much lower stakes than proving an alibi in court so I see how this model would work.
Earlier quoted context omitted.
That's amazing, so cool. Is that something Google's not doing with the data, but could? (E.g. they don't because their maps don't show most houses precisely enough or whatever, so it wouldn't be useful?) Or is it relying on the fact that you are triangulating or similar from the known exact position of your WiFi routers or similar down to the inch, and Google doesn't have any way of knowing that?
Or they do and have internally assessed that it would be too creepy to provide to users, but are happily using it to better target advertising.
By the way, I'm pretty sure I've seen that Google's advertising targeting is only allowed to use "neighborhood level" location, which is designed to be coarse enough to not allow specifying individual people.
>can use a single [private] key regardless of which randomized version of her public key was used to encrypt. I have not seen this before. Trying to wrap my brain around how this works. In terms of ECC I thought public and private were a single pair. Can anyone explain what is going on with public key randomization?
Warning: this is baseless speculation from someone with only a semester of cryptography experience. If you asked me to implement "randomized public keys" I would generate a master key pair (MPUB and MPRIV). Then, I would combine MPRIV and a random value N in a one-way function to make a new key K. I would use K as effectively a "random public key" and use it as if it was MPUB (the one-way function would have to outpu…
Couldn't "random value N" just be a nonce that only Apple knows?