![]() I also concur with I don't think it's a problem to grant access to "Chrome Safe The Keychain is part of macOS and is like a "secure wallet" where the operating system and its applications can store passwords and other sensitive data such as certificates. So, curious initial design decisions on Vivaldi's part aside, I don't think that there's any reason to get too upset about this. Yep that is the plan with a way to automatically migrate the passwords over but that is for a future release. I took that opportunity to ask is there a why Vivaldi doesn't use "Vivaldi Safe Storage"? Vivaldi has also accidentally created and used "Chromium Safe Storage" in a few snapshots, which caused people to lose access to their passwords when Vivaldi switched to the new data store. (Like others that got the Keychain access prompt, I wondered what was going on.) My guess is that it's either to facilitate data import from Chrome or to maintain compatibility with Chrome for some obscure reason. I don't know why Vivaldi chose to use "Chrome Safe Storage" as well. For some reason, Vivaldi uses the same key name. ![]() It's generated after installation during Chrome's initial setup. ![]() "Chrome Safe Storage" in the Keychain is simply an application password that Chrome uses to encrypt/decrypt data in its secure information store.
0 Comments
Leave a Reply. |