277432 - A bad password registrated fill the log file on the server

Status: RESOLVED EXPIRED

(Toolkit :: Password Manager, defect)

Description

[Christian Robidas]

On our intranet(IIS), all users must be logged on with their network account. 
One user try Firefox to surf on our Intranet. He work also on another web site 
inside the organisation. On this other web site, the username is the same than 
the intranet but not the password. The password manager remember this password 
well. When the user try to logon the intranet, the user enter the password for 
the other site and he quit his place. The password manager enter into a loop : 

1 - It try to login in with the bad password
2 - The server return a 401 require authentification and log this action into 
the event log. 
3- The password manager receive this error but the user is not at his desk to 
prevent the error and the password manager retry with the bad password

This loop fill the event log with around 20 hits per seconds. It's not a 
problem for few secondes but the amount of log grow rapidly with the time.

Comment 1

[Daniel Veditz [:dveditz] (OOO: back Aug 26)]

This doesn't sound like a security problem requiring the confidential flag, but
I'm not sure I understand the problem description. The mention of the 401
response makes it sound like we're talking about HTTP auth. The networking
library would send an auth response automatically, but only if it's a good
password, not if we got an error back. The password manager *never* submits
anything to the network, it only fills in dialogs and the user has to be present
to submit.

I'm having trouble figuring out how either mechanism could be responding 20
times a second.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.