Closed
Bug 777691
Opened 12 years ago
Closed 9 years ago
password doorhanger popup doesnt show fqdn
Categories
(Toolkit :: Password Manager, defect)
Toolkit
Password Manager
Tracking
()
RESOLVED
DUPLICATE
of bug 1175300
People
(Reporter: gaston, Unassigned)
Details
Dunno if this is a real bug or a design decision (nor if it was already reported, couldnt find a dupe) but the 'do you want to save passwd?' popup doesnt show the fqdn of the requesting website. Ie if i visit www.foo.com, or dev,foo.com or prod.foo.com it will only show 'foo.com' in the popup, while this can be three different websites. The saved passwd is correctly associated with the fqdn in the passwd manager though.
Dunno what happens too for www.foo.com/bar and www.foo.com/quux, which could also be two different auths. They only show foo.com in the popup, so this might be misleading.
Checked with 14.0.1 and trunk.
Comment 1•12 years ago
|
||
I don't know the password manager code that well but it seems that it is saving the hostname and not only the domain. Is the doorhanger only prompting the domain for some reasons?
OS: OpenBSD → All
Hardware: x86 → All
Version: unspecified → Trunk
Comment 2•12 years ago
|
||
This is intentional, from bug 403420. The fqdn is stored internally, but the displayed string is kept short. Helps prevent overly-wordy prompts.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
Comment 3•12 years ago
|
||
[reopening, to make sure the comment is seen]
I wonder if only showing the domain instead of the host can't be misleading and provides security risks. If we really care about saving space, can't we simply remove the website name? Given that we are using a doorhanger, it seems like the user is having enough context and we wouldn't provide potentially misleading information to the user.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Comment 4•9 years ago
|
||
Fixed by bug 1175300 + bug 1144856
Status: REOPENED → RESOLVED
Closed: 12 years ago → 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•