feat: expose safestorage backend information on linux - #38873
Conversation
|
@deepak1556 the Windows test failures seem to be caused by this PR. |
|
Hmm that should be unlikely since the changes are guarded for linux. Let me rebase on latest |
cfad7bb to
6e1e0ac
Compare
|
@deepak1556 looks like this is affected by https://chromium-review.googlesource.com/c/chromium/src/+/4609704 |
|
Release Notes Persisted
|
|
I was unable to backport this PR to "25-x-y" cleanly; |
|
I was unable to backport this PR to "24-x-y" cleanly; |
|
/trop run backport-to 26-x-y |
|
The backport process for this PR has been manually initiated - sending your PR to |
|
I have automatically backported this PR to "26-x-y", please check out #39107 |
|
/trop run backport-to 26-x-y |
|
The backport process for this PR has been manually initiated - sending your PR to |
|
I have automatically backported this PR to "26-x-y", please check out #39155 |
|
@deepak1556 has manually backported this PR to "25-x-y", please check out #39325 |
* feat: expose safestorage backend information on linux * Remove gnome-keyring Refs https://chromium-review.googlesource.com/c/chromium/src/+/4609704
Description of Change
It is currently not possible to determine why encryption is not available on Linux at runtime (i-e) which backend was attempted to be initialized. It is possible to get these information via
--vmodule="*/components/os_crypt/*=1"but having the information at runtime would be helpful for applications to surface better error to users. The PR introduces two new APIsafeStorage.getSelectedStorageBackend()to retrieve the preferred storage backend informationsafeStorage.setUsePlainTextEncryption(usePlainText)to allow using the weaker plain text password for the encryption key, can be used as default when no storage backends are available on Linux.Checklist
npm testpassesRelease Notes
Notes: Add
safeStorage.setUsePlainTextEncryptionandsafeStorage.getSelectedStorageBackendapi