Duplicate login names and passwords



Passwords & Permissions
6 years ago
6 years ago


(Reporter: Chris Burton, Unassigned)


SeaMonkey 2.5 Branch
Windows XP

Firefox Tracking Flags

(Not tracked)




6 years ago
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:8.0.1) Gecko/20111121 Firefox/8.0.1 SeaMonkey/2.5
Build ID: 20111121045514

Steps to reproduce:

Tried to create a new Profile and move it from C:\ to D:\

Actual results:

I wound up with double, triple and quadruple UserNames and Login Passwords (same name and password listed in Password Manager 2, 3, and 4 times).

Expected results:

Uh, it shouldn't have?

Comment 1

6 years ago
1. how did you create your new profile?
2. How did you move it to D:?

Are you sure that the hosts/sites are the same? Including same port number, etc.

Comment 2

6 years ago
Hi Philip,

I followed the directions listed on the Mozilla "Moving Profile" (or something like that) page. "It" wouldn't move or do anything. Also, when I'd go to one of my e-mail accounts (I have more than one on Google) I used to get a dropdown box that listed my user account names in SeaMonkey 1.x. Now, with 2.5 I have to type in the first letter just like with IE. And, even on sites where I only have one user name and password, I still have to type in the first letter. SM 1.x would automatically enter the info when I went to the page.

Is there something I need to set? Or is this an "improvement" in 2.5?
In reply to comment #2

Normally, username and password should be filled-in by the PM.
In "Edit → Preferences → Privacy & Security → Passwords → Manage stored passwords", check that you don't have spurious or duplicate entries and delete what (if anything) is not wanted. (You may have to display passwords in order to determine which entries you may want to delete.)

When you have several usernames for a single account, try hitting down-arrow before you type anything in, and see if it helps.
Component: General → Passwords & Permissions
QA Contact: general → privacy

Comment 4

6 years ago
Hi Tony,

Quote: "Try hitting the down-arrow ... "

I do that now: Type the first letter (or hit the ▼). My b***h is that I HAVE to. In SM 1.x when I went to Google Mail, a box would pop-up with my accounts and I could just click the one I wanted: I didn't have to hit or type anything. Is this supposed to be an improvement? Is there any way to get the SM 1.x style back?

As far as Passwords goes, when I delete the extra one, the whole thing disappears — both from the window and from the list on the left. ?????? I have to close out and restart PW Manager.

And, Why are there so many duplicates in the first place????? About half the sites I go to where I DON'T have more than just me, I have to hit the ▼ and the rest of the sites auto-fill the UserName and PW.  ??????

I really don't understand how this is an improvement.

Comment 5

6 years ago
@Tony & Philip,

I got my profile moved (finally) and I went to PW Manager and deleted all the extraneous stuff.

However, having to type in the first letter of my user name or clicking in the userID box and then having to hit the ▼ and click my log in name is really getting to be annoying — especially since I only have one name at most sites.

For example, when I come here "cold" (clicking on a bookmark) my user name and PW are auto-entered. However, when I go to WindowsBBS, no matter what I do, I have to do the click\type thing to login. I even deleted my info from PW Manager, re-logged into WindowsBBS and checked "remember me" and still no joy.
Am I missing something?

Comment 6

6 years ago
If the page at: http://the-edmeister.com/firefox_info/articles/List_Firefox-3_Passwords.htm is used to see the Hosts/usercode/password information the duplicate entry situation would be explained.  

Password Manager only shows the "Website"/user/password.  It does not show the "Submit URL" address which can be different than the "Website" address.

Also there is a difference in http:// https:// for a "Website"

You could end up with multiple entries for one "Website" looking at Password Manager.  But the .htm file above will show that the "Submit URL" is different for each one.  Therefore there are no "duplicates"

Check the thread "Re: 2.6.1 stored passwords - multiple redundant repeats over and over" in Mozilla.support.seamonkey

Comment 7

6 years ago
Hi Ed,

Thanks for the link, but it was written in 2007 and for FireFox. I noticed that you modded it in 2008. I saved it and I'll run it when I close out.

One thing I did notice is that the poster included a link to <i>here.</i>

However, you said, ""Password Manager only shows the "Website"/user/password.  It does not show the "Submit URL" address which can be different than the "Website" address.""

OK, then why didn't I have this thing with SM 1.x? And, I know about http and https, but the duplicates, triplicates, etc.,  are for both — which the poster (DoctorBill)was wondering about, too.

Might it have something to do with SM 1.x (et al) xxxxxx.s file now being a "signons.sqlite" file?

Comment 8

6 years ago
A short answer to your question about SM 1.x to 2.x, the answer is Yes.
I'm not up on the differences though.

And the link, even though for FireFox, it DOES work with SM 2.6.1 and earlier.
By using it and looking at the output you will see the sub-domain or sub-URL as the .htm output calls it.

As to why it didn't happen in 1.x (I looked at some old printouts and only found one entry for the host sites) I have no idea.  Possibly the 1.x SM programmers did not see any reason to keep the sub-domains visible or maybe the fact that the user/password remained the same there was no need to display the duplicates.

Your guess is as good as mine.
(In reply to Ed from comment #8)
> A short answer to your question about SM 1.x to 2.x, the answer is Yes.
> I'm not up on the differences though.

SeaMonkey 1.x to 2.0 is when the "Great Toolkit Migration" happened. I suppose that the password manager was one of the interfaces which were rewritten to use the familiar SeaMonkey (and Mozilla Suite, and Netscape) UI on a new (Toolkit-based) backend.
You need to log in before you can comment on or make changes to this bug.