Sorry FDSC people, I'm going to break it for you again soon. Attempting to deploy a light version of OAuth on metasmoke so that you don't have to be logged in to use the write API, and so that you're not passing cookies cross-domain.
Yeah, it'll be fixed. But there'll be a period between metasmoke updating and the script updating where one or the other will be using the old auth method, incompatible with the new one.
@FrankerZ Follow the link, it just is a shortened link to another SO question. (as a side note, I think that code is plagarized from a blog post but I forgot to flag it)
@hichris123 It goes through 2 particularly nasty link shortening services (1 lets you track visitor's ips and one lets you change the destination anytime)
A SO moderator deemed it fit to destroy the user based on this post due to this
OK: So #1 we have multiple redirects. While this may redirect to stackoverflow now, it may not in a day. This was investigated before I made the decision of spam. #2: Even if it didn't redirect through multiple redirects, there is 0 reason for a url shortener (It was an href, and no where did the link show in the post). Also: The url service captured user information. Users could sell that information, it could be wingding looking for ip addresses to ddos...
@hichris123 Fully plagiarised with only the link changed out for something that could extremely easily be edited into obnoxiously hard to catch spam by a user with no other contributions member since today
@Andy I disagree with them :P a static public IP plus a static internal IP would enable you to identify a device, so that combination would be PII. A MAC address can be spoofed easily, so I wouldn't say that you can reasonably link it to a device. They're not intended to be unique, and if you have one you can't say "it was this person" or "it was this computer", so I don't see how they're PII.
@ArtOfCode If I get your phone's mac address (say, from following you with a wireless sniffer and watching your phone send out probes for wireless networks in the area) I can easily determine which mac is yours (you were the only one to travel from A to B to C to D). Now I know who you are, where you are, how long you were there...and I'd like to see you know that I'm doing it and you change your phone's MAC.
You don't need an IP for the mac to give you away. Your mac is sent with EVERY transmission your phone makes - "Hello?! Any network out there?" or "Hi new network! I'd like an IP please"
Whelp: I'm standing behind my decision for that, and I guess I'll have to eat an invalidated feedback on that, but for the record, I disagree with that decision. While it's something that may take a bit of digging into: It was ultimately determined as such, and the user was destroyed over it.
> Instead, businesses generally use “cookies” to track consumers’ activities and associate those activities with a particular computer or device. . . . [H]owever, it may be possible to link or merge the collected information with personally identifiable information – for example, name, address, and other information provided by a consumer when the consumer registers at a website.
Mac, in combination with other stuff, makes it very easy to identify a person
@Andy sure, I agree with them there. If you have a combination of stuff, various information, you can identify someone. If you've just got a MAC, or a MAC plus a public IP, you can't.
@undo of course, I may have completely overlooked some glaring security hole, in which case we have a problem. Yeah. Second set of eyes on this before you deploy it would be good
@ArtOfCode "stuff" is easily gotten though by visiting a link. Drop a cookie in the user's browser and now you can track their activities. Or, if you are less friendly, malware.
@Andy gonna disagree again, I'm afraid... sure, you can drop a cookie on them. It'll only get sent to you, though. So, if you're a link shortener, you'll be able to match up my IP and potentially MAC address with the websites I'm visiting, and you'll have a city-level rough location. I still don't think that's PI.
tomanthony.co.uk/blog/detect-visitor-social-networks - Not sure if that's still possible, but that JS code is to check if a user is logged into Google, Facebook or Twitter. Drop that on your url shortner and you have information about a user as they pass through
Unless someone is spoofing your phone number as part of a test, I can be assured that if I see your number pop up on my caller ID, that it would be your device (Within 90% certainty).
Still disagree. How do you get from having my phone number to identifying precisely which one of the world's 14 billion devices I'm using, with 90% certainty?
The only way I know how would be to call up your carrier, make up some sob story about having a stroke and forgetting all my passwords, but I want to confirm (for fire-insurance purposes) that I had an iPhone and correct me if I'm wrong.
And I have two SIM cards here, remind me which one is for my phone and what the IMEI should be?
You certainly wouldn't that kind of information over the phone in the UK, though. Data protection makes it illegal to provide PII without first identifying that you're speaking to the owner of it or their authorized agent.
Essentially this. App has an API key. App needs an API token to use for write operations. Tokens are tied to the API key and the user, so each user-app combination has a distinct write token. App sends the user to MicroAuth#request, using its API key. Metasmoke asks the user if they want to authorize the app. If user says yes, user gets given a code to enter in the app. App uses this code and its API key to go to MicroAuth#token, where it can get hold of the write token.
@ArtOfCode Working on those deployment issues, so might move your recent commits to a new branch. I still plan on deploying them, but want to deal with one potential problem at a time ;)