You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
Hi! We are using keytar in Tutanota desktop app and we recently came across a use case on Linux with cancelling unlock prompt from GNOME Keyring daemon. When we cancel the prompt Keytar returns null for getPassword(). It does the same when we unlock the keychain but the key is not there. Because of that we can't distinguish whether we should generate a key or not.
We suspect that it does not handle cancellation from libsecret properly (there's a Cancellable argument to secret_password_lookup_sync which is not used).
Are we missing something or is it really not possible to distinguish these cases now? Thanks!
The text was updated successfully, but these errors were encountered:
Hi! We are using keytar in Tutanota desktop app and we recently came across a use case on Linux with cancelling unlock prompt from GNOME Keyring daemon. When we cancel the prompt Keytar returns
null
forgetPassword()
. It does the same when we unlock the keychain but the key is not there. Because of that we can't distinguish whether we should generate a key or not.We suspect that it does not handle cancellation from libsecret properly (there's a
Cancellable
argument tosecret_password_lookup_sync
which is not used).Are we missing something or is it really not possible to distinguish these cases now? Thanks!
The text was updated successfully, but these errors were encountered: