when you say next cycle it's version 19.04 or something else ? like
19.10 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824969
Title:
gnupg2 : pinentry cache is not clear : gpg-agent
To manage n
It's commited upstream and in Debian so we will get it when next Ubuntu
cycle start. Then we can look at doing a SRU but for that we need a
testcase which can be used to verify the SRU (and ideally which doesn't
require buying hardware like an yubikey)
--
You received this bug notification becaus
** Changed in: gnupg2 (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824969
Title:
gnupg2 : pinentry cache is not clear : gpg-agent
To manage notific
I just see the fix is committed, when will we see it ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824969
Title:
gnupg2 : pinentry cache is not clear : gpg-agent
To manage notifications about th
it's exactly the same procedure has describe in Debian bug.
In fact I configure a yubikey with a ssh key inside.
Whenever I try to connect somewhere, where I'm sure my pub key is I get:
sign_and_send_pubkey: signing failed: agent refused operation
--
You received this bug notification because
Thank you for your bug report. Do you have steps that can be used to
trigger the issue?
** Bug watch added: Debian Bug tracker #919856
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919856
** Also affects: gnupg2 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919856
Im
