Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Nummer anzurufen, sie per SMS zu kontaktieren oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Saved logins disapeared after upgrade to version 82.0.2 (64-bit)

  • 7 Antworten
  • 1 hat dieses Problem
  • 29 Aufrufe
  • Letzte Antwort von andre.zuquete

more options

My FF updated to version 82.0.2 (64-bit).

The file logins.json apparently contains all saved logins that I had before the upgrade. However, none shows up when nedded. I've added some that where already there and a new entry was created, at the end of the array of entries. I could not see why (1) the already existing entry could not be used and (2) the new entry did not replace the old one.

Regards,

Ausgewählte Lösung

I gave up. The logins' protection process is so cumbersome that not even a security guy (me) will attempt to find out what is wrong. I just recovered old (last week) copies of the critical files from a backup and everything is back to normal.

Diese Antwort im Kontext lesen 👍 0

Alle Antworten (7)

more options

Open the Password Manager. Is the login data still there?


In the event that the passwords information is lost, you should record all information in a separate text file somewhere else on your hard drive, or written down. You can easily copy and paste if you need to do so. If you are concerned about someone else looking at that file, you can compress it using a password.

Hilfreich?

more options

I cannot see any password with the Password Manager, not even any registered login (and I have 466 of them). Except the new ones (like the one I've created for accesing this forum) created after the upgrade. The old ones are still in the logins.json file but not "active".

Hilfreich?

more options

You can set signon.debug = true on the about:config page and close Firefox. After restarting Firefox you can check the Browser Console for logins related messages.

You can open the about:config page via the location/address bar. You can click the button to "Accept the Risk and Continue".

Hilfreich?

more options

It is what I suspected: the way usernames and passwords are encrypted apparently changed, and all saved logins from previous versions cannot be recovered. Is this correct? If yes, what can I do?

Login crypto: Prompted for a master password, notifying for passwordmgr-crypto-login crypto-SDR.js:302:10 LoginManager: Getting a list of all logins asynchronously LoginManager.jsm:434:9 Login storage: _searchLogins: returning 430 logins for Object { }

with options 

Object { schemeUpgrades: false, acceptDifferentSubdomains: false } storage-json.js:635:10 Login crypto: Failed to decrypt string: MDoEEPgAAAAAAAAAAAAAAAAAAAEwFAYIKoZIhvcNAwcECChlUxGozxNABBC0B7ezuvTYXt7ZSigi+i4R (NS_ERROR_FAILURE) crypto-SDR.js:184:12 Login storage: Could not decrypt login: {bfc42278-7b66-4636-af1f-6d80745dee5b} storage-json.js:430:18 NS_ERROR_FAILURE: Couldn't decrypt string crypto-SDR.js:200

Hilfreich?

more options

It seems tobe what I suspected: the way credentials are encrypted changed, and previous values cannot be recovered. Is this correct?

Login crypto: Prompted for a master password, notifying for passwordmgr-crypto-login crypto-SDR.js:302:10 LoginManager: Getting a list of all logins asynchronously LoginManager.jsm:434:9 Login storage: _searchLogins: returning 430 logins for Object { }

with options 

Object { schemeUpgrades: false, acceptDifferentSubdomains: false } storage-json.js:635:10 Login crypto: Failed to decrypt string: MDoEEPgAAAAAAAAAAAAAAAAAAAEwFAYIKoZIhvcNAwcECChlUxGozxNABBC0B7ezuvTYXt7ZSigi+i4R (NS_ERROR_FAILURE) crypto-SDR.js:184:12 Login storage: Could not decrypt login: {bfc42278-7b66-4636-af1f-6d80745dee5b} storage-json.js:430:18 NS_ERROR_FAILURE: Couldn't decrypt string crypto-SDR.js:200

Hilfreich?

more options

The previously reported problem happened in a Windows 10 (64-bit). Apparently it doesn't happen in a Ubuntu Linux (Budgie, 18.04.5 LTS) with Firefox 82.0.

Any help?

Hilfreich?

more options

Ausgewählte Lösung

I gave up. The logins' protection process is so cumbersome that not even a security guy (me) will attempt to find out what is wrong. I just recovered old (last week) copies of the critical files from a backup and everything is back to normal.

Hilfreich?

Stellen Sie eine Frage

Sie müssen sich mit Ihrem Benutzerkonto anmelden, um auf Beiträge zu antworten. Bitte stellen Sie eine neue Frage, wenn Sie noch kein Benutzerkonto haben.