Bill the forum is not perfect. I accept it. I hope you do as well (
there is nothing bad in not to be perfect). What we are doing is - trying to improve our experience for the forum. You, me, everyone who cares about the forum we all are doing the same. It's theymos's and other admins job what to chose and what not to coz they know better than you and me on what exactly need to do for the forum. They are the ultimate deciders.
You believe that it is a fairly advanced that doesn't read stickies or educate themselves on the security of their accounts?
This was really insulting without prior knowledge about me.
On March 20th I calculated my logged in time per day was 2 hours 13 minutes,
now it's gone to (approximately calculated) 3 hours 10 minutes/day!. It's around 16 hours a week.
My question is spending purely 16 hours a week is a lot of time for a forum. Don't you think I read a lot on the forum also write?
Anyway the topic was about the security issue and let's be in it. It's no good bringing another dimension on the topic.
I see the fears and I share them with you guys. The security question has been proven to be a security flaw and so most people do not even have one set, from what I understand. I think it is goofy that it operates the way it does, too. I wish that it was fixed as much as the next user, because it's like a booby-trap to lock someone out of their own account. I imagine that with the new forum software being developed this will be a problem of the past.
Let's say I agree with you. The most don't even set one but the least (including me) who set, I guess they are the most serious BitcoinTalk users, right?
Those most do not care much may be so, they don't look for any security. Don't we need to think about those least serious BitcoinTalk users in this case?
1.
It should not be like to deal with bunches of codes. In the front panel part, a little html change can disable users to take input of Secret Question.
<input type="text" name="SecretQuestion">
The standard one<input type="text" name="SecretQuestion" disabled>
With disabled attribute.
Closely see the difference. It's only adding a
disabled attribute in the HTML will not allow the users to set a secret question.
2.
On the password remainder page just delete the HTML cheackbox that represents for ask me my question.
These should not be harder than unlocking a lot of locked account for Secret Question issue. Plus the amount of hassle the members go through on recovering the locked account I guess.