-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Exception when using libykcs11.dll with Cygwin ssh #428
Comments
One thing that springs to mind is the issue Windows has with different runtime libraries in different dll:s within a single process. This could easily lead to crashes like we see here. The latest YubicoPIV Tool is linked against the VS 2019 dll runtime. |
Looks like this is the reason why my |
@JasonHK yeah I also ran into this when using git originally (see git-for-windows/git#4296 in case you need a workaround).
Thanks that's helpful info. I didn't get around to asking about this issue with cygwin yet. Would it help to verify if Cygwin git is linked against a different version of a particular dll? |
Im reasonably certain that it is. They wouldn't be using Visual Studio Runtime. A way to check dependensies is by using the utility called depends.exe, you will easily find it by googling. I'd point out that is pretty dated by now, so it throws some warnings when run on recent Windows version. |
I'd say that the proper solution for this case would be to build yubico-piv-tool under cygwin, and then use that binary. Unfortunately we don't officially support that. If you do get that to work and contribute it to the projekt it would be greatly appreciated. |
Hello,
I'm running into the following issue with
libykcs11.dll
from yubico-piv-tool-2.3.1-win64.msi. When using it with ssh from Cygwin, I'm observing an exception:ssh.exe.stackdump
The version of the ssh from Cygwin used is:
The exact same incantation works as expected when using ssh bundled with windows, i.e.
This version is
Any ideas whether it's an issue with how libykcs11.dll is built or with Cygwin's ssh.exe?
Thanks
The text was updated successfully, but these errors were encountered: