Feed Advanced Search

Mar 6 2018

gniibe added a comment to T3825: Scdaemon needs to restart after wake up from sleep mode for YubiKey to work on Windows.

I realized that suspend/resume is not supported yet on GNU/Linux: https://anonscm.debian.org/cgit/pcsclite/PCSC.git/tree/TODO#n7
So, I can't test myself.
Here is an attempt to improve:


The reference is: https://stackoverflow.com/questions/11294638/how-to-use-scardgetstatuschange-correctly-on-windows-8

Mar 6 2018, 2:11 AM · gpg4win, gpgagent, gnupg (gpg22), scd, Windows, Bug Report, yubikey
gniibe added a comment to T3825: Scdaemon needs to restart after wake up from sleep mode for YubiKey to work on Windows.

It looks like SCardGetStatusChange doesn't return failure after wake up.
Here, what we need is catching the event of wake up, which requires reset of the card.
I think that we can check by the dwEventState field.
I'll try on GNU/Linux environment, then ask you to try.

Mar 6 2018, 12:41 AM · gpg4win, gpgagent, gnupg (gpg22), scd, Windows, Bug Report, yubikey

Mar 5 2018

vovcacik added a comment to T3825: Scdaemon needs to restart after wake up from sleep mode for YubiKey to work on Windows.

@werner there had to be some mix up, as the log snippet is not mine.

Mar 5 2018, 9:26 PM · gpg4win, gpgagent, gnupg (gpg22), scd, Windows, Bug Report, yubikey
werner added a comment to T3825: Scdaemon needs to restart after wake up from sleep mode for YubiKey to work on Windows.

This seems to be the relevant part of the log:

2017-11-18 07:45:15 scdaemon[8918] DBG: ccid-driver: CCID: card inactive/removed
2017-11-18 07:45:15 scdaemon[8918] ccid open error: skip
2017-11-18 07:45:15 scdaemon[8918] pcsc_establish_context failed: no service (0x8010001d)
2017-11-18 07:45:15 scdaemon[8918] DBG: ccid-driver: CCID: interrupt callback 0
2017-11-18 07:45:15 scdaemon[8918] DBG: ccid-driver: CCID: card removed
Mar 5 2018, 1:46 PM · gpg4win, gpgagent, gnupg (gpg22), scd, Windows, Bug Report, yubikey
vovcacik updated the task description for T3825: Scdaemon needs to restart after wake up from sleep mode for YubiKey to work on Windows.
Mar 5 2018, 11:22 AM · gpg4win, gpgagent, gnupg (gpg22), scd, Windows, Bug Report, yubikey
vovcacik changed the visibility for T3825: Scdaemon needs to restart after wake up from sleep mode for YubiKey to work on Windows.
Mar 5 2018, 11:17 AM · gpg4win, gpgagent, gnupg (gpg22), scd, Windows, Bug Report, yubikey

Nov 14 2017

JochenSaalfeld closed T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried as Resolved.

Tested with Gpg4win-3.0.0-beta17 with GpgOL-2.0.2-beta8 on Windows 10 (64bit) with Outlook 2016.

Nov 14 2017, 1:55 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows

Nov 13 2017

aheinecke reassigned T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried from aheinecke to JochenSaalfeld.

Jochen could you please test this on one of our test VM's again and resolve this then?

Nov 13 2017, 10:23 AM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows

Oct 26 2017

gniibe closed T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon as Resolved.
Oct 26 2017, 5:50 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report

Oct 24 2017

gniibe added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

I am closing this bug report, as I can't get feedback to fix something.

Oct 24 2017, 2:42 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report

Oct 20 2017

werner edited projects for T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon, added: gnupg (gpg22); removed gnupg.
Oct 20 2017, 1:30 PM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
werner removed projects from T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon: gnupg (gpg20), gnupg (gpg21).

gniibe: Can you check the status?

Oct 20 2017, 1:28 PM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report

Sep 6 2017

gniibe triaged T3386: gnupg: make check fails on cygwin on 64-bit Windows as Low priority.

Please try this patch:

Sep 6 2017, 11:45 AM · Windows 64, gnupg, Bug Report

Sep 5 2017

bjmgeek created T3386: gnupg: make check fails on cygwin on 64-bit Windows.
Sep 5 2017, 8:14 PM · Windows 64, gnupg, Bug Report

May 14 2017

aheinecke added a commit to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: rX8c3c8dbd7b5c: Use c++ hardening flags.
May 14 2017, 7:27 PM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
aheinecke removed a parent task for T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: T3103: Release Gpg4win 3.0 stable.
May 14 2017, 1:49 PM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
aheinecke added a comment to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL.

GpgEX is now also compiled with ASLR + DEP. I still have to check some other binaries of Gpg4win before I close this task but I no longer see it as blocking a 3.0 release where I wanted to have this included.

May 14 2017, 1:49 PM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32

Apr 24 2017

aheinecke added a parent task for T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: T3103: Release Gpg4win 3.0 stable.
Apr 24 2017, 5:45 PM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32

Apr 4 2017

kai removed a project from T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: Duplicate.
Apr 4 2017, 3:03 PM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
kai moved T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL from Backlog to Done on the Duplicate board.
Apr 4 2017, 2:53 PM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
kai merged T2171: ASLR and DEP not enable in EXE and DLL's into T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL.
Apr 4 2017, 2:52 PM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32

Mar 30 2017

admin created Windows 64.
Mar 30 2017, 6:42 PM

Jan 23 2017

werner removed a project from T2814: Fallback to CSIDL_PROGRAM_FILESX86 doesn't work: Testing.
Jan 23 2017, 11:23 PM · gpgme, Bug Report, Windows 64, Windows
werner closed T2814: Fallback to CSIDL_PROGRAM_FILESX86 doesn't work as Resolved.
Jan 23 2017, 11:23 PM · gpgme, Bug Report, Windows 64, Windows

Dec 8 2016

yeti closed T2860: Yubikey Sucessfully detected by Win7 but gpg --card-status fails as Resolved.
Dec 8 2016, 12:06 AM · Bug Report, Windows 64, scd, Windows, gnupg, Windows 32
yeti added a comment to T2860: Yubikey Sucessfully detected by Win7 but gpg --card-status fails.

I tested with the GnuPG version 2.0.30 (GPG4WIn) as well as the current 2.1.16
Windows binaries. SCdaemon was running but was unable to get exclusive card access.
Why?
The Cisco Network Manager as well as Cisco Anyconnect VPN did both gain shared
card access (they were not told to do so!). I needed both programs to get access
to the university network.

Uninstalling both Programs and restarting did resolve the issue. To find the
two offenders I used Process Explorer (Processes for all users) and used the
Find Handle or DLL functon with the search term "SCARD". All crosschecked all
Processes (except for scdaemon which sould access the card) and Services
(svchost) to be only scdaemon aswell as the services to be Windows internal.
To determine the inital issue I used
https://sourceforge.net/projects/pcsctracker/ which told me the status of my
Yubikey (as Present,InUse -> Shared Access).

As a suggestion I like to see the experimental option to change the accessmode
from exclusive to shared on the commandline (If for example the other
application cannot be uninstalled).

Dec 8 2016, 12:06 AM · Bug Report, Windows 64, scd, Windows, gnupg, Windows 32
yeti set Version to 2.1.16 2.0.30 on T2860: Yubikey Sucessfully detected by Win7 but gpg --card-status fails.
Dec 8 2016, 12:06 AM · Bug Report, Windows 64, scd, Windows, gnupg, Windows 32

Dec 7 2016

gniibe added a comment to T2860: Yubikey Sucessfully detected by Win7 but gpg --card-status fails.

Which version of GnuPG are you using? Do you have scdaemon?

Dec 7 2016, 9:38 AM · Bug Report, Windows 64, scd, Windows, gnupg, Windows 32
gniibe claimed T2860: Yubikey Sucessfully detected by Win7 but gpg --card-status fails.
Dec 7 2016, 9:38 AM · Bug Report, Windows 64, scd, Windows, gnupg, Windows 32

Dec 2 2016

yeti added projects to T2860: Yubikey Sucessfully detected by Win7 but gpg --card-status fails: Windows 32, gnupg, Windows, scd, Windows 64, Bug Report.
Dec 2 2016, 12:17 AM · Bug Report, Windows 64, scd, Windows, gnupg, Windows 32

Nov 16 2016

aheinecke reopened T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried as "Open".
Nov 16 2016, 10:13 AM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke removed a project from T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried: Unreleased.
Nov 16 2016, 10:13 AM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke added a comment to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried.

I've just announced a new 3.0 beta that contains the updated GpgOL

http://lists.wald.intevation.org/pipermail/gpg4win-devel/2016-November/001659.html

Please let me know if it still crashes for you with that version.

Nov 16 2016, 10:13 AM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke added a project to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried: Testing.
Nov 16 2016, 10:13 AM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows

Nov 11 2016

ralfbergs added a comment to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried.

Thanks a lot. I will test as soon as you release the test build.

Nov 11 2016, 6:11 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke closed T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried as Resolved.
Nov 11 2016, 6:04 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke added a project to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried: Unreleased.
Nov 11 2016, 6:04 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke added a comment to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried.

I've tried this again with the current development version after a very large
refactoring how we handle mails. The bug appears to be gone. I've tested 10
times to send a file with closed / open outlook and with and without encryption
active.

If I install gpg4win-2.3.3 on the same system / setup the crash is reliably
reproducible.

It's still likely that we made a reference counting error internally in code
that was changed / fixed now. And Outlook released the Mail object too early and
crashed.

Kaspersky probably had some similar error in their code.

I'll upload a new Gpg4win beta with the new gpgol next. I'll ping in this issue
once thats done so you could ideally confirm that its fixed now.

Nov 11 2016, 6:03 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows

Nov 4 2016

werner added a project to T2814: Fallback to CSIDL_PROGRAM_FILESX86 doesn't work: Testing.
Nov 4 2016, 8:16 AM · gpgme, Bug Report, Windows 64, Windows
werner added a comment to T2814: Fallback to CSIDL_PROGRAM_FILESX86 doesn't work.

Fixed with commit df08a0c. Thanks.

Nov 4 2016, 8:16 AM · gpgme, Bug Report, Windows 64, Windows

Oct 31 2016

sdl_nexiom.net added a comment to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL.

That's awesome aheinecke! Honestly wasn't sure if this issue would ever get much
attention. Thanks for the effort in making Gpg4win a more secure product!

Oct 31 2016, 2:18 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32

Oct 28 2016

aheinecke claimed T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL.
Oct 28 2016, 10:57 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
aheinecke added a comment to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL.

GpgOL is built with DEP and and ASLR now. Need to enable this for GpgEX and some
other parts of Gpg4win, too. So not yet fully resolved but I keep it in mind.

Oct 28 2016, 10:57 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32

Oct 25 2016

ticho added projects to T2814: Fallback to CSIDL_PROGRAM_FILESX86 doesn't work: Windows, Windows 64, Bug Report, gpgme.
Oct 25 2016, 10:50 AM · gpgme, Bug Report, Windows 64, Windows

Oct 17 2016

shtrom added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

I run in the same issue as PRab whenever I suspend or hibernate my machine. The
machine as Broadcom BCM5880 with a smart-card reader, so I cannot unplug it.
Quickest workaround is to kill/restart scdaemon.

Is there/could there be a command that could be sent to scdaemon via the agent
so a reset could be triggered? It should be easy enough to line that up as part
of the resume scripts.

Oct 17 2016, 11:17 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report

Aug 12 2016

ralfbergs added a comment to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried.

Interesting...

The Kaspersky issue is about Outlook 2007... Is that supposed bug really already
THAT old?!

Aug 12 2016, 10:05 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke added projects to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried: gpg4win, Windows 32.
Aug 12 2016, 6:24 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke added a comment to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried.

This could be a nasty one. The crash occurs after the data structure of the mail
was unloaded in outlook and GpgOL already completely detached it's event
handlers from the object and frees up the memory. GpgOL is not executing any
code when the crash occurs. That outlook blames GpgOL is likely because it jumps
into an invalid memory region that was allocated for GpgOL but is no longer
valid. This shouldn't happen though as we have already successfully unregistered
all our callbacks.

So I currently think that somehow when using send from explorer outlook through
some side effect / bug does a callback into GpgOL's event handling code which
was already destroyed. I'll try to confirm that theory on monday by keeping the
event handlers around after the unload event occurred.

Also does not appear that we are the first ones with that problem:
https://forum.kaspersky.com/index.php?showtopic=225375

:-/

Aug 12 2016, 6:24 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
ralfbergs added a comment to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried.

Thanks! :-)

Aug 12 2016, 4:18 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke added a comment to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried.

Thanks for the report. I am able to reproduce the problem.

Looking into it.

Aug 12 2016, 12:41 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke lowered the priority of T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried from Unbreak Now! to High.
Aug 12 2016, 12:41 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
aheinecke claimed T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried.
Aug 12 2016, 12:41 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows

Jul 13 2016

ralfbergs added a comment to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried.

To make it clear: I'm not even trying to sign or encrypt, just send a plaintext
message with attachment also in the clear.

Jul 13 2016, 12:48 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
ralfbergs set Version to 1.4.1.5 on T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried.
Jul 13 2016, 12:16 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows
ralfbergs added projects to T2416: Outlook 2016 64-bit: Crash if "Send to" > "Mail Recipient" is tried: Windows, gpgol, Windows 64, Bug Report.
Jul 13 2016, 12:16 PM · Testing, Windows 32, gpg4win, Bug Report, Windows 64, gpgol, Windows

Jul 5 2016

aheinecke closed T2295: Provide 64-bit gpgol.dll for new 64-bit versions of Office as Resolved.
Jul 5 2016, 2:47 PM · Windows 64, Feature Request, Windows, gpgol
aheinecke added a comment to T2295: Provide 64-bit gpgol.dll for new 64-bit versions of Office.

Gpg4win 2.3.1 and 2.3.2 included 64 bit versions of gpgol.

Jul 5 2016, 2:47 PM · Windows 64, Feature Request, Windows, gpgol

May 27 2016

werner lowered the priority of T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL from High to Normal.
May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
werner added a comment to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL.

Duplicate of T2171

May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
werner removed a project from T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: Bug Report.
May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
werner added a project to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: Duplicate.
May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
werner added a comment to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL.

You can now. Thus is not a bug but a feature request.

Note that we do not use Microsoft compilers but use gcc and in cross build
environment.

May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32
werner added a project to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: Feature Request.
May 27 2016, 9:54 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32

May 23 2016

sdl_nexiom.net added projects to T2366: No DEP/ASLR or other security mitigations for GpgEX/GpgOL: Windows 32, Windows, gpg4win, gpgol, Windows 64, Bug Report.
May 23 2016, 4:48 AM · Feature Request, Windows 64, gpgol, gpg4win, Windows, Windows 32

Mar 29 2016

werner removed a project from T2295: Provide 64-bit gpgol.dll for new 64-bit versions of Office: Bug Report.
Mar 29 2016, 1:22 PM · Windows 64, Feature Request, Windows, gpgol
werner added a comment to T2295: Provide 64-bit gpgol.dll for new 64-bit versions of Office.

Actually we are working on a 64 bit version.

Mar 29 2016, 1:22 PM · Windows 64, Feature Request, Windows, gpgol
werner added a project to T2295: Provide 64-bit gpgol.dll for new 64-bit versions of Office: Feature Request.
Mar 29 2016, 1:22 PM · Windows 64, Feature Request, Windows, gpgol
werner lowered the priority of T2295: Provide 64-bit gpgol.dll for new 64-bit versions of Office from Unbreak Now! to Wishlist.
Mar 29 2016, 1:22 PM · Windows 64, Feature Request, Windows, gpgol

Mar 25 2016

RAnders00 added projects to T2295: Provide 64-bit gpgol.dll for new 64-bit versions of Office: Windows, Windows 64.
Mar 25 2016, 1:21 PM · Windows 64, Feature Request, Windows, gpgol
bernhard added a project to T2293: gpg-agent + smartcard not asking for PIN with PUTTY: Not A Bug.
Mar 25 2016, 11:36 AM · Windows 64, gnupg (gpg20), Bug Report, gpg4win, gnupg, Windows, Not A Bug
bernhard added a comment to T2293: gpg-agent + smartcard not asking for PIN with PUTTY.

Thanks for testing 2.1 and for reporting the results.
Good to know that it works now.

Mar 25 2016, 11:36 AM · Windows 64, gnupg (gpg20), Bug Report, gpg4win, gnupg, Windows, Not A Bug
bernhard closed T2293: gpg-agent + smartcard not asking for PIN with PUTTY as Resolved.
Mar 25 2016, 11:36 AM · Windows 64, gnupg (gpg20), Bug Report, gpg4win, gnupg, Windows, Not A Bug
timtim added a comment to T2293: gpg-agent + smartcard not asking for PIN with PUTTY.

I have good news : gpg 2.1 rocks !
Problem solved and here is the solution :

As Sijie said, the "smartcard compatible" pageant was loading the SIG key and
the AUTH key.

Unfortunately, under gpg 2.0.x, when you export a public key and use gpg2ssh,
the output is the ssh key for the SIG key (and not the auth).

So when using gpg-agent, it was waiting for putty to request the AUTH key and
not the SIG key (as it should !). The "smartcard enabled" pageant was sending
the SIG key so it was working with it.

Now for the good part : with gpg 2.1, we can now natively use --export-ssh-key,
and this command export the AUTH key, so in the end, it works :)

Thank you everyone for the help, and I hope it can helps other people too !

Can we close this bug please ?

Regards

Mar 25 2016, 9:07 AM · Windows 64, gnupg (gpg20), Bug Report, gpg4win, gnupg, Windows, Not A Bug

Mar 24 2016

timtim added a comment to T2293: gpg-agent + smartcard not asking for PIN with PUTTY.

For history purpose, and trying to maximize information, I have been asked to post some part of the discussion I have
on the mailing list about this problem. Here it is :

I tried older version (of gpg4win) (which, at the time, worked for people with the
same setup as myself), but I can try new version too of course.

That is helpful, because development right now is concentrating more
on Gpg4win 3 with the new GnuPG 2.1 (to become 2.2) and this is where
gpg-agent and pinentry is handled slightly differently. So making sure that
it works with the new version is better for the future.

Ok, I installed gpg4win 3.0.0 BETA 128.
The problem stay the same, no pin is asked.

In the mean time, I tried this tool : http://smartcard-auth.de/ssh-en.html
It replace the pageant.exe that ships with putty. And it works. When I
log on the server with putty, I got asked for the PIN. So I think this
is not a problem with the smartcard or with keys. It seems that it's
only that gpg-agent doesn't trigger the pinentry.

I tried witht gpg-agent on another computer (fresh install) running Windows 7 x64, and
with another smartcard, same problem : no pinentry asked.

Mar 24 2016, 5:40 PM · Windows 64, gnupg (gpg20), Bug Report, gpg4win, gnupg, Windows, Not A Bug
timtim added a comment to T2293: gpg-agent + smartcard not asking for PIN with PUTTY.

Yes gpg-agent is started before, I can see it in the process list (and even the scdaemon process).

In fact, pageant can't be started at the same time as gpg-agent (I suppose it share the same mutex because it
says "pageant is already running" when I try to start pageant while gpg-agent is already running).

Mar 24 2016, 5:33 PM · Windows 64, gnupg (gpg20), Bug Report, gpg4win, gnupg, Windows, Not A Bug
werner updated subscribers of T2293: gpg-agent + smartcard not asking for PIN with PUTTY.
Mar 24 2016, 5:15 PM · Windows 64, gnupg (gpg20), Bug Report, gpg4win, gnupg, Windows, Not A Bug
werner added a comment to T2293: gpg-agent + smartcard not asking for PIN with PUTTY.

Did you start gpg-agent before putty or pageant?

Mar 24 2016, 5:15 PM · Windows 64, gnupg (gpg20), Bug Report, gpg4win, gnupg, Windows, Not A Bug
bernhard updated subscribers of T2293: gpg-agent + smartcard not asking for PIN with PUTTY.
Mar 24 2016, 2:26 PM · Windows 64, gnupg (gpg20), Bug Report, gpg4win, gnupg, Windows, Not A Bug
bernhard added projects to T2293: gpg-agent + smartcard not asking for PIN with PUTTY: Windows, gpg4win, gnupg (gpg20), Windows 64.
Mar 24 2016, 2:26 PM · Windows 64, gnupg (gpg20), Bug Report, gpg4win, gnupg, Windows, Not A Bug

Mar 17 2016

werner added a comment to T2088: create revocation certificate on cp850 consoles [windows].

and there is no w64 version of 1.4

Mar 17 2016, 3:54 PM · Won't Fix, Bug Report, gnupg (gpg14), Windows, gnupg, Windows 32
werner added a comment to T2088: create revocation certificate on cp850 consoles [windows].

We won't fix such things for 1.4 (Windows)

Mar 17 2016, 3:54 PM · Won't Fix, Bug Report, gnupg (gpg14), Windows, gnupg, Windows 32

Mar 16 2016

PRab added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

I believe I have also seen this issue (or something very similar) on my Windows
7 64bit machine. I am running gpg 2.1.11. I hope this isn't redundant, but it
seems that I need to restart scdaemon anytime I unplug/replug my yubikey or
suspend/resume my computer.

Sometimes it doesn't recover even after restarting scdaemon. In those cases, I
am able to fix it by stopping scdaemon, removing the yubikey, starting scdaemon,
and finally reinserting the yubikey.

Mar 16 2016, 9:01 PM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report

Dec 22 2015

Mario set Version to 1.2 on T2202: struct timespec is already defined in MINGW32.
Dec 22 2015, 5:03 PM · In Progress, Bug Report, Windows, npth
Mario added projects to T2202: struct timespec is already defined in MINGW32: npth, Windows 32, Windows, Windows 64, Bug Report.
Dec 22 2015, 5:03 PM · In Progress, Bug Report, Windows, npth
gniibe added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Thank you again.

It is likely that the token itself doesn't work well after wakeup from sleep
mode. In this case, all that we can do is re-inserting the token manually.

I'm not sure how PC/SC service handles USB reset after wakeup.

Dec 22 2015, 8:43 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Dec 22 2015, 7:52 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Sorry to say, but mapping the error to "no reader" doesn't help. The first
reset event doesn't get handled. Later it trys to remove the reader but it's
not getting correctly resetted/reinserted again.

I've attached the debug log again

Dec 22 2015, 7:52 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
gniibe added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Thank you for further testing.
I think that current code doesn't handle the case when card goes inactive/reset
while reader keeps working. Current code only goes to the reset sequence for a
card again when it detects reader failure. So, although the concept is
different, I think mapping PSCS_W_CARD_RESET to SW_HOST_NO_READER (for now) will
work. Given the situation we don't yet support multiple cards, this workaround
would be OK for a while.

Dec 22 2015, 2:10 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Dec 22 2015, 12:35 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Nope. Neither mapping the "reset card" event to SW_HOST_CARD_INACTIVE or
SW_HOST_NO_CARD helps. It seems that somewhere in the code the return code
SW error codes are not being handled correctly and the card doesn't get
resetted.

I've attached a small log where you can see that pcsc returns the error
reason "reset card" which then gets remapped to "Card reset required" (was
general error before). I also can see that the error is getting mapped to
GPG_ERR_CARD_RESET (because of the error message "Card reset required")
leaving the daemon around with no working card and reporting general errors
again (0x100b).

Additional Info: This bug only happens when you put your computer/laptop
into sleep mode while the smartcard/reader (yubikey) is plugged in. If I
remove the reader before putting it to sleep and attaching it after getting
out of the sleep mode, the scdaemon works fine.

Dec 22 2015, 12:35 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report

Dec 21 2015

dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

D338: 740_0002-scd-map-card-reset-event.patch

Dec 21 2015, 11:29 PM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Maybe it's more appropriate to map the PSCS_W_CARD_RESET event to the
SW_HOST_CARD_INACTIVE error code which later gets mapped to GPG_ERR_CARD_RESET
error code.

I've attached the patch file. It would make sense to backport this mapping as
well. Right now it's not yet tested.

Dec 21 2015, 11:29 PM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

I found another problem with the smartcard service under windows. Putting
the system into sleep mode and waking it up again creates an 0x80100068
error code (aka PCSC_W_RESET_CARD).

I'll test if it helps to map the RESET_CARD event to the same REMOVE_CARD
event to get the card reactivated after sleep mode.

Logfile:
2015-12-21 22:16:57 scdaemon[10040] DBG: send apdu: c=00 i=CA p1=00 p2=C4
lc=-1 le=256 em=0
2015-12-21 22:16:57 scdaemon[10040] DBG: PCSC_data: 00 CA 00 C4 00
2015-12-21 22:16:57 scdaemon[10040] pcsc_transmit failed: reset card
(0x80100068)
2015-12-21 22:16:57 scdaemon[10040] apdu_send_simple(0) failed: general
error

Dec 21 2015, 10:35 PM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report

Dec 11 2015

gniibe added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Thank you for your testing.

Your change is pushed with my comment:
http://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=d1a97585c5e73fbc7d4cf90e38f76ffc5aea305f

I'll backport this to GnuPG 2.0.

Dec 11 2015, 1:07 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report

Dec 10 2015

dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Dec 10 2015, 3:33 PM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Here's the logfile with all the errors (guru debug level) vanilla 2.1.10

Dec 10 2015, 3:33 PM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Dec 10 2015, 3:32 PM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

After some time spending fighting with the build tools of gnupg (cross compile
for windows under debian) I managed to build the installer with my patched
file.

Most important: The most common error thrown is the 0x8010001e
(E_SERVICE_STOPPED) This is the important one. The other error 0x8010001d
(E_NO_SERVICE) is only thrown in the transition from ok to stopped. So only
sometimes.

This was my process:

git clone git://git.gnupg.org/gnupg.git
cd gnupg
git checkout tags/gnupg-2.1.10
./autogen.sh
cat ../0001-scd-Fix-removal-of-unplugged-usb-readers.patch | patch -p1
sed -i -e 's/^SELFCHECK=1/SELFCHECK=0/' build-aux/speedo.mk
make -f build-aux/speedo.mk w32-installer

I've created new logfiles (vanilla 2.1.10 und patched 2.1.10) to show the
difference and confirm that it'S actually working now :-)

Dec 10 2015, 3:32 PM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
dhoffend added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

I'm okay with signing off the commit. I can test this for Windows 8.1 or 10,
my only problem is that I'm not able to compile gpg for windows right now. Or
are there instructions somewhere on how to achieve this?

Dec 10 2015, 9:11 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report
gniibe added a comment to T2167: Unplugging USB Smartcard/Yubikey causes problems with scdaemon.

Thank you again.

I think that Windows 8 (and later) changed the PC/SC service. The service is
only available when smartcard is there, and after the removal, it returns
PCSC_E_NO_SERVICE error. This is not expected for current code.

I'm applying your patch with my comment like above. Do you agree to put the
line in the commit log?:

   Signed-off-by: Daniel Hoffend <dh@dotlan.net>

I don't have Windows 8 machine. So, I leave this issue as testing.

Dec 10 2015, 3:15 AM · gnupg (gpg22), Testing, patch, Windows 64, scd, Windows, Windows 32, Bug Report