Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

Re: Re: Re: We blame tye.

by no_slogan (Deacon)
on Mar 22, 2002 at 19:03 UTC ( #153631=note: print w/ replies, xml ) Need Help??


in reply to Re: Re: We blame tye.
in thread We blame tye.

A tech site like this can get away with just sending people a new auto-generated password
Then someone could hassle me by repeatedly requesting password changes on my account. If they did it every 5 minutes, I could hardly use the site at all. The server could impose a rate limit on password changes, like only one per day or so. That would eliminate the full-blown denial of service, but I'd still have to go check my e-mail for the new password, which might be inconvenient.


Comment on Re: Re: Re: We blame tye.
Re: Re: Re: Re: We blame tye.
by perrin (Chancellor) on Mar 22, 2002 at 19:29 UTC
    This is true. I'm not sure there's a good way to deal with all possible attacks like this.

    As an aside, I often go to sites that have "mail me my password" features, request my password, and then realize I signed up under a different name. Then I wonder what the guy who just got the password reminder mail is thinking.

Re: Re: Re: Re: We blame tye.
by QwertyD (Pilgrim) on Mar 22, 2002 at 23:08 UTC

    To get around this, some sites ask the user for a hint question when they register. If the user forgets their password, they must answer their hint question (which they hopefully still remember), and supply some other personal information (which is verified against the info they provided upon registering). A new password is generated and emailed only if the above are correct. I'm pretty sure Yahoo does this for My Yahoo, Yahoo Mail, and the like.

    Another idea would be to generate a new password, but revert to the old one after, say, ten minutes if the user doesn't log in and change it. In this case, you would still let the user log in with the old password within those ten minutes. I realize this might not be easy to impliment ontop of an existing username/password database, though.

      We could ask for your e-mail address and "real name" before we would reset your password. But I'll just be happy to not include the password in the "edit user" HTML code and to require that the password be reentered in order for you to be able to change it.

      I'd also like to see https supported (which might also solve the "too many dirty words counted at the firewall" problem for particle). I have yet to even looked into how hard that would be, though.

              - tye (but my friends call me "Tye")
      If the user forgets their password, they must answer their hint question (which they hopefully still remember), and supply some other personal information (which is verified against the info they provided upon registering).
      Unfortunately, easy to remember == easy to guess (especially if it's someone you know), and "other personal information" is usually not hard to find with some research. Sometimes, you won't know the real identity that goes with someone's online persona, so that won't get you anywhere. Sometimes, you will, though. That solution is probably better than nothing, though.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://153631]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others surveying the Monastery: (7)
As of 2014-08-20 11:53 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The best computer themed movie is:











    Results (111 votes), past polls