On Dec 23, Stéphane Glondu <[email protected]> wrote: > - What kind of profile are you operating on? Firefox? Thunderbird? Which > versions? Firefox, latest unstable.
> - Did it work at some point in the past?
Never used it before.
> - Do you get the error with any request? Including '' (the quoted empty
> string)?
Yes.
> > Fatal error: exception Main.NSS_decrypt_failed("~dWx0cmFzZWNvbmRhcnk=",
> > -8183, 0)
>
> The "~" looks suspicious. Is the string the same as the one you give to
> pwdecrypt?
No. it actually comes from this entry for a long-dead service:
{"id":39,"hostname":"https://www.ultradns.net","httpRealm":null,"formSubmitURL":"","usernameField":"sponsortag","passwordField":"","encryptedUsername":"~dWx0cmFzZWNvbmRhcnk=","encryptedPassword":"irc.oregonstate.edu:80
(Nagios
Access)","guid":"{7123e2c1-4cb7-422f-9f3e-4cb7980dab17}","encType":0,"timeCreated":1278853271263,"timeLastUsed":1278853271263,"timePasswordChanged":1278853271263,"timesUsed":1}
Which now I wonder how it has been mangled over time, since that was not
the password...
I have a few other entries where encryptedUsername starts with a ~ and
the encryptedPassword is a URL.
Interestingly, none of these can actually with the search function of
about:logins.
> From looking at nss sources, error -8183 corresponds to
> SEC_ERROR_BAD_DER, i.e. "improperly formatted DER-encoded message".
Indeed: I wonder what DER has to do with this, but ~ is not valid in
a base64 string.
So now I think that the problem is that the program is choking on these
malformed encryptedUsername fields.
OTOH, why does it decode all usernames before finding the actual entry
that I am searching for?
--
ciao,
Marco
signature.asc
Description: PGP signature
