Martin Preuss wrote:
Hi,
On Friday 03 November 2006 00:40, Andrey Jivsov wrote:
[...]
I was thinking to implement the cyberJack PIN pad reader support.
Unfortunately, I ran into a problem when I must reset the reader with
usb_reset(device_handle). However, I don't see ifd_device_ops.reset
[...
Martin Preuss wrote:
Hi,
On Friday 03 November 2006 00:40, Andrey Jivsov wrote:
[...]
I was thinking to implement the cyberJack PIN pad reader support.
[...]
Just curious: Are you implementing support for both types of Cyberjack devices
(0x100 and 0x300, even though they look identical they
Andreas Jellinghaus wrote:
Andrey Jivsov wrote:
I was thinking to implement the cyberJack PIN pad reader support.
that is a good idea! if I can be of any help please let me know.
I thought about it myself, but never found time for that (and most
likely neither will anytime soon, so please go a
Douglas E. Engert wrote:
Please consider adding the attached patch to pkcs15-gemsafe.c
which I originally sent August 10. This version is against
the 0.11.2-pre2.
committed.
Cheers,
Nils
___
opensc-devel mailing list
opensc-devel@lists.opensc-projec
Jesus Luna wrote:
Dear all,
I'm trying to add HSM support to our OCSP Responder by integrating
engine_pkcs11 with openssl to it, however in our tests we have found that
RSA Signature operations are not implemented
Do you mean: signing ocsp responses with openssl (the command
line tool ?) doesn
Hi
> I've noticed that the wiki is not up to date in this section
> (http://www.opensc-project.org/opensc/wiki/GermanEid). According to the
> Datev Homepage, the Smart Card is based upon the Telesec TCOS 2.03 MIN
> and the Siemens SLE66CX322P-Microchip (http://datev.de/info-db/0903358).
>
> opens
Hi,
I've noticed that the wiki is not up to date in this section
(http://www.opensc-project.org/opensc/wiki/GermanEid). According to the
Datev Homepage, the Smart Card is based upon the Telesec TCOS 2.03 MIN
and the Siemens SLE66CX322P-Microchip (http://datev.de/info-db/0903358).
opensc-explorer
Jesus Luna wrote:
I'm trying to add HSM support to our OCSP Responder by integrating
engine_pkcs11 with openssl to it, however in our tests we have found that
RSA Signature operations are not implemented and in fact that seems to be an
active ticket (#7 "Please support rsautl sign"). Are there an
Dear all,
I'm trying to add HSM support to our OCSP Responder by integrating
engine_pkcs11 with openssl to it, however in our tests we have found that
RSA Signature operations are not implemented and in fact that seems to be an
active ticket (#7 "Please support rsautl sign"). Are there any plans to
Hi Johannes,
It requires modification of g/kdm, something we intend to
suggest/propose/modify in the future.
--
Regards
Signer: Eddy Nigg, StartCom Ltd.
Phone: +1.213.341.0390
Johannes Becker wrote:
Hello,
I got pam_pkcs11 working. If I use the card reader's pin pad, there
Hello,
I got pam_pkcs11 working. If I use the card reader's pin pad, there
is still the prompt to enter the PIN. No matter what you enter,
after 'return' the pinpad awakes and you can enter the PIN there.
This is a confusing behaviour, especially if you have a graphical login
with gdm or kdm.
Ho
Hi,
On Tue, Oct 31, 2006 at 07:11:19PM +0100, Andreas Steffen wrote:
> Try strongSwan from http://www.strongswan.org which has a regular
> PKCS#11 smartcard interface and allows to select certificates
> according to position e.g.
>
> leftcert=%smartcard#4
>
> which is the fourth certificate in
12 matches
Mail list logo
