Commit 51902c1c authored by mark@chromium.org's avatar mark@chromium.org

[Mac] Chromium builds shouldn't ask for access to Chrome's own secure data.

The message that this presents is:

Chromium wants to use your confidential information stored in “Chrome Safe
Storage” in your keychain. Do you want to allow access to this item?

Chromium shouldn't ask for access to Google Chrome's data, it should have its
own Chromium Safe Storage item in the keychain.

R=isherman@chromium.org

Review URL: https://codereview.chromium.org/200623002

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@261515 0039d316-1c4b-4281-b951-d872f2087c98
parent 4c437404
...@@ -51,8 +51,13 @@ std::string KeychainPassword::GetPassword() const { ...@@ -51,8 +51,13 @@ std::string KeychainPassword::GetPassword() const {
// These two strings ARE indeed user facing. But they are used to access // These two strings ARE indeed user facing. But they are used to access
// the encryption keyword. So as to not lose encrypted data when system // the encryption keyword. So as to not lose encrypted data when system
// locale changes we DO NOT LOCALIZE. // locale changes we DO NOT LOCALIZE.
#if defined(OFFICIAL_BUILD)
const std::string service_name = "Chrome Safe Storage"; const std::string service_name = "Chrome Safe Storage";
const std::string account_name = "Chrome"; const std::string account_name = "Chrome";
#else
const std::string service_name = "Chromium Safe Storage";
const std::string account_name = "Chromium";
#endif
UInt32 password_length = 0; UInt32 password_length = 0;
void* password_data = NULL; void* password_data = NULL;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment