eMediaLibrary Project
one code rather
But that does not change the security. I like having both because the user might have pressed the button twice etc
At least there aren't 5000 good passwords out there, there is just one
But we do need to slow down the requests
And I don't think it should be able to be used more than once - the idea I think is it's One Time Password/OTP
Well we can throttle both sides. only request one or two and only try a few times
yeah that we should do
I hate one time codes from my bank. :)
Haha, we all do lol
If we keep the counts down then I think its good. We can also expire them once they login ok so its one time
Keep the most recent 5 or something, max 24 hours, and only good once
A successful login should clear out all 5
A successful login should clear out all 5
Ok deal
I can do it if you want
I have the code open
Sure, do one hour expiration...
ok
This is a list searcher, that OK? Maybe should be a data searcher
Not sure we need a huge XML file of all these codes
How will you keep them from trying to login so often? Maybe we use one code only and put the retry count on it?
I would rather it email out the same code twice than make new codes.
