-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem with smartcard #124
Comments
I'm struggling with your English a bit. Please provide: Smartcard model, operating system environment details, whether you're using a CAPI/PKCS/FIDO, and ideally a video of the behavior if possible. |
Sorry for my English ... I posted 2 videos. Not working: putty and pageant 0.8: https://www.youtube.com/watch?v=CNqnDfhLY6c
|
That is crazy. I haven't seen any behavior like that before. Do you see the same long waiting behavior if you do not Pageant? PuTTY / Pageant did change mechanism they use to communication from Windows messages to named pipes so it's possible that's also playing a role here. Does anyone else see this behavior? |
@walt31 Can you link me to the product page for the token you have? |
I put another video (https://www.youtube.com/watch?v=w43nnmHDJc8): Change from puttycac 0.76U1 to 0.80 Otherwise the link to the documentation of the product: |
Dear community, Developpers,
Not sure a bug, but I encounter a difference between v0.76u1 and upper.
I use pageant with a smartcard and puttycac.
With v0.78 an newer, each time I open a new window, I have to wait a long time, then a window appear requesting me to validate access to the smartcard.
In v0.76u1, first connection is waiting accessing the card + pin code, but all other connection are quick and functional.
I try cross test, and it seems that the problem is located in putty. Currently, I test pageant 0.8 (32 bits) with putty 0.76u1 and work perfectly.
Tested with 0.78u1, 0.79 and 0.8: putty hang for a while, then request me, for all connection (not only the first), to validate the smartcard tool then session abort due to latency. Restart the connection and after another 20 to 30s connect the VM.
So: problem in configuration? bug?
I saw that the 0.8 menu have some new items. Maybe I forget some settings.
Thanks for the feedback
The text was updated successfully, but these errors were encountered: