>>950288 (OP)
It's complete bullshit. In the worst case the site will grant someone access to your account if he gets the security question right. In the best case these security questions are used on top of some other stuff, but no matter how you slice it, it's not secure. For example some site may grant someone access to your account if he has your email, IP, and secret question, but "forgot your password". Another example is a site will lock you out because your IP address changed (another invalid practice), and then require your security question on top of your password. While in this case it doesn't break your security, it's a huge pain in the ass for no reason.
>>950479
>You're doing it wrong. You SHOULD provide a fake answer here. But it should be a 2nd password, as in "ImAMassiveFaggot" or something, a sentence you'd remember or an actual secondary password.
You're doing it wrong too. You're decreasing your password strength so that you can remember multiple passwords for a single account on a single website. The only proper way is to treat each security question as a separate password that gives access to your account, and store the passwords. Of course it's better to just not use such retarded sites in the first place. A more respectable web service that exists today is cock.li, which, while it requires JS, it only makes you use one password.
>Security is difficult
nope
>and there isn't a single good security method.
yep, cryptographic authentication, and failing that (because you're using webshit): a single password
>This is why you register with email/phone number
no. that's worse
>and have stuff like andOTP/google authenticator.
no.
>>950431
yeah, why am I not surprised that the security questions apologist goes off talking about password hashing after 3 seconds?
>>950831
>a phone number is a sure way to identify a user as an individual person
no it fucking isn't, doofus