Closed
Bug 233340
Opened 21 years ago
Closed 16 years ago
Password Manager: should exclusively store passwords from URLs
Categories
(Toolkit :: Password Manager, defect)
Toolkit
Password Manager
Tracking
()
RESOLVED
INVALID
People
(Reporter: benc, Unassigned)
References
(Depends on 3 open bugs, Blocks 1 open bug)
Details
(dup checked before filing) choffman made an interesting point today: all passwords should be stored in password manager. This bug is a tracking bug for that idea, as far as passwords in URL's go. Please do not link up bugs that have to do w/ other features, this is passwords in URLs ONLY. --- As far as implementation, I think the general idea is that we need to be trapping entry points where passwords are used, and making sure password manager is called for storage, while removing the password from the URLs. This would prevent the propgration of URL's w/ passwords (into history, into bookmarks, as forwarded mail, into client generated content, etc.)
Comment 1•21 years ago
|
||
what if password manager is disabled? I don't think people would be happy if they couldn't follow links on (non-anonymous) ftp servers with pw mgr disabled...
Comment 2•21 years ago
|
||
We should make sure password manager gets a crack at storing these, but only in the same way it ever does -- if not disabled it asks the user whether they want to store the password or not. We can't make it mandatory (shared machines, super sekret passwords, kiosk set ups, etc.).
ostgote@gmx.net found some more...
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•19 years ago
|
Assignee: dveditz → nobody
Updated•16 years ago
|
Component: Passwords & Permissions → Password Manager
Product: SeaMonkey → Toolkit
QA Contact: password.manager
Comment 4•16 years ago
|
||
Old bug with unclear purpose --> INVALID.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•