In the next few days I will build the scripts for installing all files
and automatically build initrd/initramfs and then will be in a
position to test it. As I pointed out above I already tested
pcsc-lite-libs+OpenCT+OpenSC (without anything else) and it works to
absolute perfection, so
Mr Dash Four wrote:
I already tested pcsc-lite-libs+OpenCT+OpenSC
Why do you need pcsc-lite-libs?
Spotters badge!
Executing rpm -qRp on the newly-built package gives me
pcsc-lite-libs(x86-64) so, naturally, I assumed that was needed (the
package contains two .so files, so not much of a
I already tested pcsc-lite-libs+OpenCT+OpenSC
Why do you need pcsc-lite-libs?
Spotters badge!
Executing rpm -qRp on the newly-built package gives me
pcsc-lite-libs(x86-64) so, naturally, I assumed that was needed (the
package contains two .so files, so not much of a difference
2010/10/23 Peter Stuge pe...@stuge.se:
Andre Zepezauer wrote:
In other words, build a wrapper around libccid with an api
compatible with libpcsclite.
Then I think it would be a better idea to make a p11 provider
directly on top of libccid.
That may work. But Mr Dash Four wrote he also need
Then I think it would be a better idea to make a p11 provider
directly on top of libccid.
That may work. But Mr Dash Four wrote he also need OpenCT.
Since he do not give the list of readers he wants to use I can't really help.
You already know that I am using Aladdin eToken 64k.
On Sat, 2010-10-23 at 05:37 +0200, Peter Stuge wrote:
Andre Zepezauer wrote:
In other words, build a wrapper around libccid with an api
compatible with libpcsclite.
Then I think it would be a better idea to make a p11 provider
directly on top of libccid.
Your approach may be useful only
In other words, build a wrapper around libccid with an api
compatible with libpcsclite.
Then I think it would be a better idea to make a p11 provider
directly on top of libccid.
That may work. But Mr Dash Four wrote he also need OpenCT.
Since he do not give the list of
Mr Dash Four wrote:
the simple job of reading a data token from the smartcard
It's not at all simple. I guess it seems simple when you run
pkcs11-tool, but there is a lot going on behind the scenes.
Any ideas anyone?
You need to do some development, to allow also minimal environments
to
Hello,
On Sat, 2010-10-23 at 16:13 +0100, Mr Dash Four wrote:
In other words, build a wrapper around libccid with an api
compatible with libpcsclite.
Then I think it would be a better idea to make a p11 provider
directly on top of libccid.
That may work. But Mr Dash
Mr Dash Four wrote:
I already tested pcsc-lite-libs+OpenCT+OpenSC
Why do you need pcsc-lite-libs?
//Peter
___
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
Hello,
you could use something like this:
pkcs15-crypt --key 3b8d4e --input cipher.bin --decipher -R
The only requirement is libpcsclite. Everything else could be turned
off. Correct?
If you don't want a running pcscd, you could try to get libpcsclite to
access the usb stack directly. In other
you could use something like this:
pkcs15-crypt --key 3b8d4e --input cipher.bin --decipher -R
The only requirement is libpcsclite. Everything else could be turned
off. Correct?
You've lost me!
I already have the data object stored on my smartcard and I need a
stripped-down
Andre Zepezauer wrote:
In other words, build a wrapper around libccid with an api
compatible with libpcsclite.
Then I think it would be a better idea to make a p11 provider
directly on top of libccid.
//Peter
___
opensc-devel mailing list
Mr Dash Four wrote:
I already use libpcsclite, but there are other dependencies on (mainly)
openct as well as the pcsc-lite libraries you mention (libdbus-1.so.3,
libhal.so.1 are two of those).
That is not the fault of packages - blame your distribution for that.
What you want is
14 matches
Mail list logo
