Closed
Bug 27910
Opened 25 years ago
Closed 25 years ago
Master Password refused after being set
Categories
(SeaMonkey :: Passwords & Permissions, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M14
People
(Reporter: mikepinkerton, Assigned: morse)
Details
(Whiteboard: [PDT+])
- start with a profile that doesn't have single signon enabled (not saving mail
password, etc)
- click the "i want to save my mail password" checkbox next time you check your
mail.
- fill out the single-signon master password dialog, entering your password twice
- quit the app
- relaunch and try to read mail or check your single-signons.
- you'll get the "enter your master password" dialog. enter your password.
expected:
- it accepts it
results:
- invalid password dialog, asks if you want to try again.
*Mozilla* macos build from 11am 2/15/00. Not a commercial build with encryption.
The singlesignon files were created in my profile directory and the prefs look
like they are setup correctly in my prefs.js, but I can't tell if everything is
right because most of it is gobbledy-good.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M14
Assignee | ||
Comment 3•25 years ago
|
||
Mike, I think I know what might be going on. I got the high-order and low-order
bytes of the unichar reversed by accident. This resulted in my encoding (which
is an XOR) coming up with the high-order byte non-zero. This is a regression
that I introduced this past week.
Well this shouldn't have affected anything -- the encoded bytes written out to
the file were wrong but they'll be read in with the same mistake, cancelling out
the error. And it all was working fine on windows, although when I tried to
hand-decode the file that it generated, I realized that the file was wrong.
Now I suspect that the mac problem has to do with not being able to handle
characters that are not in the ascii character set. Due to this error, I was
writing out characters greater than 7F (hex). If I'm correct, then the fix that
I'm about to make will not work on the mac when you use non-ascii (japanese for
example) characters in your master password.
In any event, can you pull the fix that I just checked in and see if at least it
is working correct on the mac for ascii master passwords. Thanks.
The fix is in the file extensions/wallet/src/nsBasicStreamGenerator.cpp
Reporter | ||
Comment 4•25 years ago
|
||
appears to work now.
Assignee | ||
Comment 5•25 years ago
|
||
Well that's good news. Thanks for sending me your files (that helped me figure
out the problem) and for testing the fix.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 6•25 years ago
|
||
verif as fixed --tested using non-comm bits on macos 2000021608.
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•