Re: [opensc-devel] [opensc-commits] svn opensc changed[4341] pkcs11: resolve bug in C_WaitForSlotEvent() -- ' unstopped debug messages'
On Tue, 2010-05-11 at 18:08 +, webmas...@opensc-project.org wrote: Description of this bug is in http://www.opensc-project.org/pipermail/opensc-devel/2010-April/013947.html Solution: the 'rgReaderStates', used in 'wait_for_event' readers's handler, are allocated and intialized outside of the 'wait event' loop . Thank you very much for fixing this issue. When do you plan to merge your branch with trunk? -- Jean-Michel Pouré - Gooze - http://www.gooze.eu ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
[opensc-devel] openct windows
Hello, Can openct be run on windows ? How to build with for example mingw ? Just with msys like in linux versions? Regards, Bart ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] openct windows
Bart Vanherck wrote: Can openct be run on windows ? How to build with for example mingw ? Just with msys like in linux versions? Not for USB readers anyway. OpenCT could be changed to use libusb-1.0, which has some snapshots so far with Windows support. We're working on getting the code into shape for integration. OpenCT AFAIK exposes a unix socket to OpenSC, which also doesn't fit so well on Windows, but maybe that could be abstracted easily enough. //Peter ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] openct windows
It cannot run under Windows. It is harder to access USB devices under Windows... But it should be somewhat simple to port it with serial port only. On Wed, May 12, 2010 at 12:03 PM, Bart Vanherck b...@twixel.be wrote: Hello, Can openct be run on windows ? How to build with for example mingw ? Just with msys like in linux versions? Regards, Bart ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] [opensc-commits] svn opensc changed[4341] pkcs11: resolve bug in C_WaitForSlotEvent() -- ' unstopped debug messages'
Jean-Michel Pouré - GOOZE wrote: On Tue, 2010-05-11 at 18:08 +, webmas...@opensc-project.org wrote: Description of this bug is in http://www.opensc-project.org/pipermail/opensc-devel/2010-April/013947.html Solution: the 'rgReaderStates', used in 'wait_for_event' readers's handler, are allocated and intialized outside of the 'wait event' loop . Thank you very much for fixing this issue. When do you plan to merge your branch with trunk? It cannot be merged like it's now, also not all log details is clear for me. I'm still working on it. -- Viktor Tarasov viktor.tara...@opentrust.com ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
Re: [opensc-devel] Feitian ePass+SCR301 problem
Jan Just Keijser wrote:
Jean-Michel Pouré - GOOZE wrote:
On Fri, 2010-05-07 at 12:36 +0200, Jan Just Keijser wrote:
I will test it with openssl 0.9.8 next week
I think the alternative would be to generate the keys/certificates
outside the smartcard and transfer them to smartcard.
Everything is explained here:
http://www.gooze.eu/howto/smartcard-quickstarter-guide/generating-transferring-and-extracting-x-509-certificates
These are two separate test:
I can generate onboard keys if i use pcsc-lite-1.5.6-svn-* .
The second test is:
A valid private key + certificate are transferred to the smartcard
(using pkcs15-init -X/-S); I cannot sign a certificate request using the
key on the smartcard no matter which version of pcsc-lite I try. I will
try this in combination with openssl 0.9.8 this week.
I ran into this problem when trying to use the engine code with the private key,
from the openssl req command.
The load_key would always pass in FORMAT_PEM rather then FORMAT_ENGINE
The attached mode uses -keyform engine
The patch was to an early 0.9.8 version.
openssl EOT
engine dynamic - -pre SO_PATH:$OPENSC_ENGINE/engines/engine_pkcs11.so
-pre ID:pkcs11 -pre NO_VCHECK:1 -pre LIST_ADD:1 -pre LOAD
-pre MODULE_PATH:$OPENSC_PATH/opensc-pkcs11.so
version
req $SSLEAY_CONFIG -engine pkcs11 -md5 -new -key slot_0-id_$ID
-keyform engine -out cards/$1.myreq.$KEYID.pem -text
EOT
Note lines were wrapped for this e-mail.
cheers,
JJK
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
--
Douglas E. Engert deeng...@anl.gov
Argonne National Laboratory
9700 South Cass Avenue
Argonne, Illinois 60439
(630) 252-5444
--- apps/,x509.c Sat Jul 16 06:13:03 2005
+++ apps/x509.c Fri May 5 11:07:47 2006
@@ -964,7 +964,7 @@
else
{
pk=load_key(bio_err,
- keyfile, FORMAT_PEM, 0,
+ keyfile, keyformat /*FORMAT_PEM*/, 0,
passin, e, request key);
if (pk == NULL) goto end;
}
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
