Closed Bug 73931 Opened 23 years ago Closed 14 years ago

Won't remember zero-length passwords

Categories

(SeaMonkey :: Passwords & Permissions, defect)

Product:
SeaMonkey
Component:
Passwords & Permissions
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: malcolm, Unassigned)

References

Details

Problem noticed in Mozilla Mail (don't know if it's also present in browser). 
If an e-mail account has no password, the "Enter password" box always appears - 
if you leave the password field blank and check "Remember using password 
manager", the box reappears next time Mozilla is started. I.e. to get in, I've 
got to press OK on this dialog box every time I start Mozilla Mail.

I'm using Mozilla 0.7. Tried upgrading to 0.8 but the bug's still there.
This problem is probably on the calling side.  That is, the mail program should 
never have requested the dialog if it knew that there was no password needed to 
access the mail account.  Reassigning from password-manager to mail.
Component: Password Manager → Mail Window Front End
Product: Browser → MailNews
And now I'm really reassigning.
Assignee: morse → sspitzer
QA Contact: tpreston → esther
No - the mail program rightly knows that the account should have a password, 
except for this particular mail account the password is zero-length. I would 
have thought that it was the job of Password Manager to remember the password 
as normal - that it is "". This doesn't seem like the caller's fault.

But I may be wrong, on account of not knowing how it all actually links 
together.
OS: Windows ME → All
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Is this bug gonna get fixed or not? It's really gettin' on my nerves...
Keywords: mozilla0.9.2
Target Milestone: --- → mozilla0.9.2
Malcom, please read the bug guidelines (and you might also want to read the
description on what a Target Milestone is).

You are not allowed to set the Target Milestone, but rather you can nominate a
bug. The engineer working on the bug or his/her manager is in charge of when the
bug will get fixed - the Target Milestone.
Target Milestone: mozilla0.9.2 → ---
I'm not quite used to this system yet! My apologies.
(I'm the reporter) My e-mail address has changed, so CC-ing new address
(m@lcolm.org.uk).

(Sorry for spam.)
*** Bug 209841 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
*** Bug 274653 has been marked as a duplicate of this bug. ***
Next two bugs seems to have relation to null/empty/zero-length password manager
data, and are already RESOLVED/FIXED, and some bugs saying null or empty
password are closed as DUP of next bugs.
> Bug 231042 : cannot remove stored (empty) password
> Bug 221654 : Password manager prevents me from submitting this form
Does problem still exist?
Change component to Password Manager.
Component: MailNews: Main Mail Window → Password Manager
Note that in bug 274653 I saw this problem when trying to do email address
auto-complete against an LDAP server that requires binding as a user with an
empty password.

WADA, bug 231042 and bug 221654 are unrealted to this problem.  Besides, I'm
seeing this with Thunderbird 1.0.  This problem is definitely not fixed.

Seeing as how this bug is over 3 years old, is there any real hope of it being
fixed?

(In reply to comment #14)
> WADA, bug 231042 and bug 221654 are unrealted to this problem.
I see. Thanks.
 
> Seeing as how this bug is over 3 years old, is there any real hope of it being
> fixed?
There is at leaset one requirement, recently DUPed Bug 274653.
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: esther
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614
MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → EXPIRED
Ever confirmed: true

          You need to log in
          before you can comment on or make changes to this bug.