On Fri, 2018-02-09 at 10:10 +0100, Yves-Alexis Perez wrote: > On Thu, 2018-02-08 at 19:47 -0500, Daniel Kahn Gillmor wrote: > I'm adding Arnaud to the loop because he's the main developer, and I can > actually see that the last commit (https://github.com/ANSSI-FR/SmartPGP/comm > it > /78d769b671e429b6e3e7b2454b869a66f269741f) seems very relevant. > > So maybe the bug actually lies here rather than in scdaemon. > > > > can you try rebuilding with that patch removed and testing that? If > > you'd prefer i upload something to experimental for you to try without > > having to rebuild, let me know and i'll do that. > > Yes, I can try a rebuild and report back, but I'll first investigate > SmartPGP. > After a quick chat with Arnaud, it seems that even though there might be fixes to be done at the applet level, the GnuPG patch doesn't seem ready for prime time and reverting it might be a good idea. See that thread on gnupg-devel:
https://lists.gnupg.org/pipermail/gnupg-devel/2018-February/033424.html I did a rebuild with the patch disabled and I can confirm it fixes the issue for me. Regards, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part