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
I can't really explain this behavior, but when I use pass-secret-service, I see this behavior:
I restart pass-secret-service (I can't remember what, but there's some env var that gets exported into the systemd user environment, but it races against pass-secret-service so I tend to just restart it as a safe workaround)
I try to open nheko which happens to use the secret service.
When pass-secret-service attempts to decrypt, I am re-prompted to authenticate to GPG, even if I've already been using it.
The pinentry program I use tells me that my card is not available, and to insert it. If I simply remove the yubikey and re-insert it, it sees it and I'm able to proceed.
I can't quite think through what might be wrong, since I'm able to normally use GPG in every other use-case that I can think of.
Maybe it has to do with the user accessing GPG? I can understand re-authing, if that is the case, but not why I have to physically remove/re-insert in order to proceed.
The text was updated successfully, but these errors were encountered:
I think i experienced similar things. Firefox claimed the cryptodevice without being asekd after some time. And it led to sc-daemon complaining that it cannot share. Can you try disabling the crypto device things in ff?
Hi,
I can't really explain this behavior, but when I use
pass-secret-service
, I see this behavior:pass-secret-service
(I can't remember what, but there's some env var that gets exported into the systemd user environment, but it races againstpass-secret-service
so I tend to just restart it as a safe workaround)nheko
which happens to use the secret service.pass-secret-service
attempts to decrypt, I am re-prompted to authenticate to GPG, even if I've already been using it.I can't quite think through what might be wrong, since I'm able to normally use GPG in every other use-case that I can think of.
Maybe it has to do with the user accessing GPG? I can understand re-authing, if that is the case, but not why I have to physically remove/re-insert in order to proceed.
The text was updated successfully, but these errors were encountered: