Live data from Hacker News

Don't give away historic details about yourself

krebsonsecurity.com

31–40 of 207 posts

Re: Don't give away historic details about yourself

#31

A good idea to counteract privacy risks of this sort is to occasionally search yourself by your full name or by username (one that can be traced back to you, that is) across all major search engines and see if any of your data is out in the open in any public forum. Same goes for searching your phone numbers, physical addresses and your email address (preferably in double-quotes for an exact match) -- I discovered mi…

What was the mechanism by which you reported it?

Re: Don't give away historic details about yourself

#33
post #28

A good idea to counteract privacy risks of this sort is to occasionally search yourself by your full name or by username (one that can be traced back to you, that is) across all major search engines and see if any of your data is out in the open in any public forum. Same goes for searching your phone numbers, physical addresses and your email address (preferably in double-quotes for an exact match) -- I discovered mi…

Google provides a way to "subscribe" to email notifications of new search results for a given term (don't have the link handy right now). I've been subscribed to results for my full name for many years, and occasionally get an email of a new mention here and there.

I think you're referring to Google search alerts[0]. I agree, that's a pretty neat tool to be subscribed to, should be useful in drastically cutting down the response time when responding to instances of one's personally identifiable data leaking on the web.

[0] https://support.google.com/websearch/answer/4815696

Re: Don't give away historic details about yourself

#34

A good idea to counteract privacy risks of this sort is to occasionally search yourself by your full name or by username (one that can be traced back to you, that is) across all major search engines and see if any of your data is out in the open in any public forum. Same goes for searching your phone numbers, physical addresses and your email address (preferably in double-quotes for an exact match) -- I discovered mi…

What was the mechanism by which you reported it?

I reported the blog that was hosting the violating content, not the particular search result in question.

My apologies, should have made that clear in my earlier response.

Re: Don't give away historic details about yourself

#35
post #15

The whole "secret question" thing seemed to me to a completely stupid idea from the start. "Hey, give us password. If you forget your password, give us a much, much less secure way to access your account." I've always given false info to those, when I bother to fill them out at all. If necessary, I just store this false info along with the password in the encrypted file I keep my passwords in. The security questions…

SMS-based 2FA should be avoided as much as possible, since there are many ways to take over a phone number and get a hold of the code. Passwords, while being a huge hassle, is probably going to be the defacto authentication mechanism for sites and services (unfortunately). Maybe some sort of distributed PKI authentication + 2FA combo would be an interesting solution, but the problem would be adoption.

In fact this is a method of stealing people's investment accounts -- a victim with an investment account is identified. That person's phone number is then "captured". The investment account asks for 2FA and the thief now has that phone #, and "authenticates." The next step is to transfer all the money in the account to a third party and disappear.

It's disgusting how twisted these criminal activities have become.

Re: Don't give away historic details about yourself

#36

The whole "secret question" thing seemed to me to a completely stupid idea from the start. "Hey, give us password. If you forget your password, give us a much, much less secure way to access your account." I've always given false info to those, when I bother to fill them out at all. If necessary, I just store this false info along with the password in the encrypted file I keep my passwords in. The security questions…

When I signed up for a new bank account the bank rep had me set up online banking on their computer. When she asked me for my security questions and answers she was baffled when I told her the question selected didn't matter, and the answer was a seemingly random alphanumeric string. I told her that I don't know her, or her machine. For now, I'll be setting it as quick, easy for me to remember, string and I'll change…

I do this too, I was told to add something like "PLEASE MATCH THIS TEXT, THIS IS NOT A RANDOM STRING" at the beginning. Apparently when some very incompetent bank workers ask your security questions if the frauder says "oh it was just a random string, I do not remember" they give access to your account.

Re: Don't give away historic details about yourself

#37
I usually just do a random hash. Also, really, really hate the sites that do not allow you free form text the question itself and rather populate a bunch of commonly known ones. FFS, if you're a web developer working on security questions, let the user make up the question. Agreed though, we should just do away with this as an authentication factor.

Re: Don't give away historic details about yourself

#38
United Airlines is probably one of the worst I've seen: http://www.slate.com/articles/technology/future_tense/2016/0...

Not even free text but only allowing a limited set of answers via dropdown menus (most of the provided answers don't apply to me either, so it's both insecure for them and hard for me to remember as well)

Re: Don't give away historic details about yourself

#39
Using random characters for answers to "secret questions" only works when you can be 100% sure you will never have to give the answers over the phone. If you ever have to do that, random characters are worse than reality, because phone reps will just say, yeah, you're right, it's gobbledygook.

I give arbitrary answers that would make sense to something like an AI. Like, "Q: Who was your father's first employer? A: Avocado flesh" or "Q: What is your mother's maiden name? A: Rutherford B. Hayes"

Of course, all such answers are stored in my password manager.

Re: Don't give away historic details about yourself

#40

The whole "secret question" thing seemed to me to a completely stupid idea from the start. "Hey, give us password. If you forget your password, give us a much, much less secure way to access your account." I've always given false info to those, when I bother to fill them out at all. If necessary, I just store this false info along with the password in the encrypted file I keep my passwords in. The security questions…

I do the same. Once, a bank asked me over the phone what my high school mascot was (or whatever) to verify that I was really me. I hadn't expected them to use the question in this way, so I wasn't prepared to look up my answer. Knowing whatever randomly generated string I'd used was likely unpronounceable I answered, "I could teach you to pronounce it, but first you'd need to cut out your tongue." which they accepted…

This happened to me but I’d chosen the “write your own question” option, so the lady asked me “what is [childhood imaginary friend]’s middle name?” I told her the answer and she said “that was cute.” I never expected an actual person to ask me the question!
Post reply on HN