I tried all four combinations of old/new code for init and for signing.
only cards initialized with old code and signing with new code is broken,
so we could as quick fix revert the change.
also comparing log files (new init, new sign and old init, old sign)
I see these difference: the 4402 file
Hello Ludovic,
I remember doing this patch.
The problem was that the ASN.1 encoder/decoder routines were bogus.
Negative values and special values like 128 were not encoded
correctly.
I am not really surprised that cards initialized with an old version
have problems when used with a new
Am Sonntag 13 Dezember 2009 14:49:31 schrieb Ludovic Rousseau:
2009/12/13 Andreas Jellinghaus a...@dungeon.inka.de:
I tried all four combinations of old/new code for init and for signing.
only cards initialized with old code and signing with new code is broken,
so we could as quick fix
Am Sonntag 13 Dezember 2009 15:23:26 schrieb Dominik Fischer:
We have aprox. 5000 Cards initialized with 0.11.1. These cards are not
erasable. So once initialized they can't be changed I think. It's
impossible for us to exchange all the cards with new ones.
please run opensc-tool -f and show
please run opensc-tool -f and show us the permissions on
4401 and 4402, those files should be writeable with pin or so-pin,
so you will be able to fix the content of those files, if we
can write a tool for it.
The command is not supported:
$ ./opensc-tool -f
3f00 type: DF, size: 0
Am Sonntag 13 Dezember 2009 16:11:08 schrieb Dominik Fischer:
please run opensc-tool -f and show us the permissions on
4401 and 4402, those files should be writeable with pin or so-pin,
so you will be able to fix the content of those files, if we
can write a tool for it.
The command is
Am Sonntag 13 Dezember 2009 14:49:31 schrieb Ludovic Rousseau:
2009/12/13 Andreas Jellinghaus a...@dungeon.inka.de:
I tried all four combinations of old/new code for init and for signing.
only cards initialized with old code and signing with new code is broken,
so we could as quick fix
Am Sonntag 13 Dezember 2009 16:50:11 schrieb Andreas Jellinghaus:
worst case: for starcos our guess is keyReference should
be positive if it is set, so for every value from -2 to -128
we could simply add 128.
same with pinReference, it is 131 / -125
no idea how that is used etc.
but I hope we
