As this 'discussion' has now strayed beyond the confines of Android I'm moving it to The Lounge, where more general topics are appropriate.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
When you say "lookup", which database are you interested in? Start there.
No, of course not - not with data they don't need. If your bank asks you who you are meeting for dinner, don't trust them -- they don't need that information to be a custodian of your bank account. Again, the rule of least privilege trumps.
It's mitigation of needless information disclosure. Submitting a needless information disclosure is not street wise - it's naive from an information security standpoint.
Except Google. Except your phone carrier. Except some other non-google apps that harvest the data, needlessly.
Actually you are issued multiple different slave surveillance numbers potentially from one government and certainly from different other governments you have a relationship with. One SSN in the US, another number like an SSN in another country, just as you are issued one IMEI per device per person. Your point?
Logs don't care whether you've died or not. A number can last till death, or it can last for a year, either way it's still a primary key linking you to data for a duration of time.
Of course there is varying degrees of uniqueness. The SSN 078-05-1120 is used by many. Uniquely issued, but this can be manipulated. MAC addresses are also uniquely issued - no two are the same. MAC addresses can be altered, but what's issued is unique. Anyone can decide to start using uniquely issued MAC addresses as a primary key, and collect whatever data they want under that key. Same for VINs. These are unique numbers, and can be utilized to reference the data of an individual person (even if it perverts the original intent). You're letting intent control how you view the number, instead of understanding how utilitarians are making use of it.
How do you figure "easier"? It depends on the context. It's far easier for google to harvest an IMEI from device they have code running on, than to surreptitiously harvest an SSN. With SSNs already the centerpiece of identity theft, it would be a stupid legal risk for Google, as opposed to simply re-purposing something else to creep in as their own kind of SSN.
What part of the chain in the linked data are you having trouble accepting? We'll go from there.
Actually what you're replying to is fact. It's verifiable. Paranoia is a mental state, not a defense for objecting to facts. The data is traceable, or it's not. Try not to rely on emotional arguments. Tell us why you think the traceability is absent, and we can go from there.
You're presuming you've found your target to begin with. In some cases that's the end game, and the most difficult bit of information to get. Online stalkers start with much less than your present location.
The system is can be complex, but the adversary needs not be. One can break into a WEP-secured wifi AP without knowing the first detail about the system. The work has been done by others.. insiders, or skilled hackers, those with more patience.. you just need to be able to use whatever mechanism is made available to you. Or hire someone else to go through the "level 10 difficulty" process.
Frequency is only part of a threat assessment measurement. I might have a higher frequency for spilling coffee, that doesn't make it a greater damage. Getting hit by a train is pretty damaging, even though the probability is low. I'll favor 100 coffee spills over one single train hit.
Not sure where you get "extreme" concern from. Should you lose sleep over it? No. But should you be foolish enough to needlessly disclose a unique number to all apps that ask, linking a significant portion of your social life to a number, of course not. It's just being street wise- just like you don't sign your messages on this forum with your real name and SSN.
Now you're using appeal to probability logic, and failing to balance cost with risk. You can use this flawed logic to justify any number of security-naive choices.
Someone who has pics of you drunk and nude while harassing someone posts them publicly with the caption "model employee of XYZ employer", and it gets a big spotlight. Perfectly legal, as is the termination of your job that follows.. yet quite damaging.
Personally, I think it'd be *way* easier for any of those agencies to just assign some dummy PK. That's what I've done in *every* database I've ever worked on. And how would a political party get the IMEI? And who really cares if my employer gets my IMEI in a database, because the only way they'd do that is if it was a work phone. Not associated with the personal me, just at that place of employment....You could create a database of people who are in a particular political party, using the IMEI as a key (harmless in itself). Someone else could make a database of employees using IMEI as a primary key (again, harmless in itself). Someone could then put the two databases together (buy, sell, trade them), and in aggregate decide who to let go when it comes time to do layoffs. It doesn't take much imagination to realize how far data collection and aggregation goes when the same primary key becomes a part of multiple databases.
I can see all y'all's IP addresses. Be afraid.
Thats not an angry ex. Thats a psychopath. I would be far more worried whatelse shes capable of doing if she will copy your phones IMEI number. Like breaking in to your house and cutting your throat or run you down with her car. What ya do cheat on her? Sounds like she has some real issues and if your that worried about her a restraining order might be a good idea. I wouldnt worry about her knowing that number.
I can see all y'all's IP addresses. Be afraid.
I see this has suddenly become a tinfoil hat thread.
Suddenly?