Re: best way to limit # of attempts to login to protected page?
This WebDNA talk-list message is from 2000
It keeps the original formatting.
numero = 35406
interpreted = N
texte = I would maybe track the user account that break-in attempts and disable the account. Plus send e-mail to the account holder with a did you forget your password message and the site admin.The problem with using IPAdddress to lock users out is that dial-up users do not get static IPs. So then you have to block whole subnets like 123.123.123.x then you could be blocking out legit users.James Howarth ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive | Software & Site Development Suite 380 | San Diego, CA 92127 | 858.675.1106 | http://www.smithmicro.com/isd 858.675.0372 (fax)-----Original Message----- From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of John Butler Sent: Saturday, July 29, 2000 7:07 PM To: WebCatalog Talk Subject: best way to limit # of attempts to login to protected page? If I want to restrict the number of times someone can attempt to login to a protected page, what is the best way?...update a db field (with an incrementally counting number: +1 for every attempt) in a record whose key field is their IPADDRESS? And when it hits the threshhold # then disallow that IP from trying again? Then use a trigger to delete records older than (24) hours...? ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list
. To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
Associated Messages, from the most recent to the oldest:
I would maybe track the user account that break-in attempts and disable the account. Plus send e-mail to the account holder with a did you forget your password message and the site admin.The problem with using IPAdddress to lock users out is that dial-up users do not get static IPs. So then you have to block whole subnets like 123.123.123.x then you could be blocking out legit users.James Howarth ********************************** Smith Micro, Internet Solutions Div | eCommerce (WebCatalog) 16855 West Bernardo Drive | Software & Site Development Suite 380 | San Diego, CA 92127 | 858.675.1106 | http://www.smithmicro.com/isd 858.675.0372 (fax)-----Original Message----- From: WebCatalog Talk [mailto:WebDNA-Talk@talk.smithmicro.com]On Behalf Of John Butler Sent: Saturday, July 29, 2000 7:07 PM To: WebCatalog Talk Subject: best way to limit # of attempts to login to protected page? If I want to restrict the number of times someone can attempt to login to a protected page, what is the best way?...update a db field (with an incrementally counting number: +1 for every attempt) in a record whose key field is their IPADDRESS? And when it hits the threshhold # then disallow that IP from trying again? Then use a trigger to delete records older than (24) hours...? ------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/------------------------------------------------------------- This message is sent to you because you are subscribed to the mailing list . To unsubscribe, E-mail to: To switch to the DIGEST mode, E-mail to Web Archive of this list is at: http://search.smithmicro.com/
James Howarth
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WebDNA and WebSTAR Error pages (2004)
Multiple prices (1997)
two forms of delivery (1998)
checksum for credit cards? (1997)
case sensitivity in lookups (1997)
Reversed words (1997)
Protect and Serve (1999)
Problem with webcat install (1998)
Can I invoke an ssi plugin from within a webcat page (1997)
Problem with Formulas.db (1998)
stray LF character in the email (2003)
(1997)
[username][password] not showing up! HELP! (1999)
Help name our technology! (1997)
SiteGuard Use Question (1997)
new orderfile params... (2003)
can WC render sites out? (1997)
Initiating NewCart (1997)
Ranking search results (2002)
[WebDNA] WebDNA Associative Arrays? (2012)