Password decryption failed, encryption_result is 2
Reported by
kenorb@gmail.com,
Oct 8 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3235.0 Safari/537.36 Steps to reproduce the problem: I've compiled Chromium and running the browser using the old user dir by: ./Chromium --args --user-data-dir="$HOME/Library/Application Support/Google/Chrome" What is the expected behavior? What went wrong? The Chromium can't read previously stored passwords. It shows yellow username in the input field, but the password doesn't appear, instead I've information in the log that the decryption of the password failed. Log entry: [80953:199271:1008/213206.749340:INFO:login_database.cc(991)] Password decryption failed, encryption_result is 2 [80953:199271:1008/213206.752039:INFO:login_database.cc(991)] Password decryption failed, encryption_result is 2 Did this work before? N/A Chrome version: e7f0416cefe3af6fee4921a25611b0af4cedf868 Channel: canary OS Version: OS X 10.12.0 Flash Version: Is this by design? Is there any way of re-compiling the Chromium by using the same private key, or whatever it's used to read the previously stored passwords? If so, what should I do?
,
Oct 11 2017
This issue seems to be out of TE-scope. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.
,
Oct 12 2017
,
Oct 12 2017
CCing vabr@ who added the log statement.
,
Oct 16 2017
encryption_result 2 is ENCRYPTION_RESULT_SERVICE_FAILURE, which means that the Keychain seems to be temporarily unavailable. Chrome uses the Keychain to store a random byte sequence to encrypt the passwords with. If it cannot get the stored byte sequence out of the Keychain, it cannot use the encrypted passwords. Please ensure that Chrome has access to the Keychain.
,
Oct 17 2017
Chromium does not have access to the same keychain items as Chrome. The relevant item is "Chrome Safe Storage". In general, we don't support running Chrome user-data-dirs from Chromium.
,
Nov 29
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by nyerramilli@chromium.org
, Oct 9 2017