zapr-SHA-1 contains 20 bytes:
9c a9 58 e0 d8 57 59 42 7c 51 de a0 87 26 76 b0
ca 64 80 4f
The command:
pkcs15-crypt -s -i zapr-SHA-1 -p 123456 -v --pkcs1 -o signed
The output (patched libopensc):
http://akson.sgh.waw.pl/~saper/opensc/pkcs15-sign-patched-debug.log
The output with unpatched
Looks like I forgot to add --sha-1 argument to pkcs15-crypt. Is it
correct now? zapr-SHA-1 contains SHA-1 hash of some file.
% pkcs15-crypt -p 123456 -s --sha-1 -i zapr-SHA-1 --pkcs1 -o signed
Patched:
http://akson.sgh.waw.pl/~saper/opensc/pkcs15-sign-patched-debug-sha1.log
Unpatched:
Marcin Cieslak wrote:
Looks like I forgot to add --sha-1 argument to pkcs15-crypt. Is it
correct now? zapr-SHA-1 contains SHA-1 hash of some file.
% pkcs15-crypt -p 123456 -s --sha-1 -i zapr-SHA-1 --pkcs1 -o signed
Patched:
Am Dienstag, den 13.03.2007, 22:17 +0100 schrieb Andreas Jellinghaus:
Am Dienstag, 13. März 2007 17:40 schrieb Simon Eisenmann:
i today recieved the PINs for my ne D-TRUST 2048 Bit signature card
which seems to use Siemens CardOS 4.3B. I can read the certificates and
keys from the card
Here is the debug output to add some more details for this issue:
...
card-cardos.c:714:cardos_set_security_env: returning with: 0
sec.c:67:sc_set_security_env: returning with: 0
sec.c:49:sc_compute_signature: called
card-cardos.c:761:cardos_compute_signature: called
I wonder if this is one of the cards/readers that can not handle
the default max_send_size/max_recv_size = 256.
Can you try this again with the opensc.conf with these
reader_driver openct {
max_send_size = 252;
max_send_size = 252;
Or try 248 that was the old *_CHOP_*
Have you tried with
Is the OpenSC card driver missing some chaining of input code for this card?
If his card can support an RSA key = 2048 it will need to send receive
256 bytes of data. If the card can support RSA key 2048 then it
will have to read the data in multiple operations or uses extended APDUs.
This would mean that this reader does not support 2048 bit keys at all?
Schlumberger cards with 2048 bit keys work fine with this reader.
In the meantime i tried this with SCM SPR 532, SCM SCR 335 and SCM SCR
333. All give the same result.
Cheers,
Simon
Am Mittwoch, den 14.03.2007, 15:26 +0100
Simon Eisenmann wrote:
Here is the debug output to add some more details for this issue:
...
card-cardos.c:714:cardos_set_security_env: returning with: 0
sec.c:67:sc_set_security_env: returning with: 0
sec.c:49:sc_compute_signature: called
card-cardos.c:761:cardos_compute_signature: called
Hi,
i today recieved the PINs for my ne D-TRUST 2048 Bit signature card
which seems to use Siemens CardOS 4.3B. I can read the certificates and
keys from the card using opensc tools perfectly.
Though there is a problem when creating a signature (opensc svn trunk).
# pkcs15-crypt -s -k
10 matches
Mail list logo
