atom/node-keytar

Cancellation with libsecret

charlag opened this issue · 0 comments

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!