From: Evil Medi <evil_medi@hotmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Segmentation fault with openssh and pkcs11
Date: Sun, 14 Feb 2016 22:06:00 -0000 [thread overview]
Message-ID: <DUB115-W831E6382CE36CB5B5C49A983AB0@phx.gbl> (raw)
Hello Cygwin Team
As suggested by Achim, I've compiled opensc for cygwin. I used part of the build instruction from: https://github.com/OpenSC/OpenSC/wiki/OpenSC-Windows-installer, mainly: ./bootstrap && ./configure --disable-doc && make && make install. I can successfully run binaries that I've compiled this way and detect my smart card. When I run openssh with the pkcs11 libary I unfortunately still get a segmentation fault with:
command: ssh -I /usr/lib/opensc-pkcs11.dll hostanme
output: Segmentation fault (core dumped)
What are your guys thoughts?
Regards
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2016-02-14 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 22:06 Evil Medi [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-02-13 16:57 Evil Medi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DUB115-W831E6382CE36CB5B5C49A983AB0@phx.gbl \
--to=evil_medi@hotmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).