Closed Bug 174487 Opened 23 years ago Closed 23 years ago

Password manager establishing individual user/password pairs

Categories

(SeaMonkey :: Passwords & Permissions, defect)

Product:
SeaMonkey
Component:
Passwords & Permissions
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 36816

People

(Reporter: awagner, Assigned: morse)

Details

I use "chi.news.speakeasy.net" as my news access to "news.GigaNews.com". My DSL ISP provider is Speakeasy.net. Speakeasy is having problems with their latest changes to their news service and I have been getting _many_ authorization requests from their news server. In investigating the contents of my mozilla "saved passwords" under "edit/preferences/privacy and security/passwords/manage stored passwords" I found that if an "auth required" packet is received while I am in a specific News Group, instead of replying with the News Server authentication as saved for the current newsserver (chi.news,speakeasy.net), Mozilla ver 2002100604 responds by requesting I type a new "user name" and "password" sequence and posts a new username/password pair to my saved password file. Eventually I have a separate username/password pair recorded for every news group I am subscribed to.
I have found four references to this problem in the "mozilla-mail-news" mailing list with the subject "Sh*tty Netscape/Mozilla Newsreader"
Severity: major → critical
Password Manager
Product: MailNews → Browser
QA Contact: junruh → bsharma
Password Manager
Assignee: mstoltz → morse
Component: Security: General → Password Manager
QA Contact: bsharma → tpreston
Dupe of bug 36816 - news should use the _server's_ username / password when authenticating
Reporter, if you agree that this is a dupe, just mark it as such. And I think you do, since you've copied all comments from this bug to bug 36816...
*** This bug has been marked as a duplicate of 36816 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.