Andreas Jellinghaus wrote:
...
If it's property of the gemsafe card it should
be put in the card driver if it's a limitation of the reader
we should place it in the reader driver.
If I understand this correctly, setting such a limit will not
cause any problem except some extra transactions and thus delays,
right?
then I would like to add it to reader-openct or whole opensc.
restricting all readers just because some have problems ...
I don't like this idea.
the alternative would be blacklists of usb vendor/product codes
in the openct ccid driver and somehow propagate that up to opensc
/ wherever the commands can be limited to a certain size. I don't
want to go down that road unless I absolutely have too, and if
limiting all readers to 248 bytes doesn't hurt anyone, then this
is the best way from my point of view.
I don't like this ... for example the result of a 2048 bit rsa signature
generation returns a 256 byte signature and hence restricting the max
receive size to 248 makes it complicated to read the signature with T1
card.
Also I'd like to make this a config file option. I guess that some
manufacturer will produce a buggy reader, and users will need to be able
to set a lower value.
agree, we should make this value configurable (reader specific ?)
Cheers,
Nils
_______________________________________________
opensc-devel mailing list
[email protected]
http://www.opensc-project.org/mailman/listinfo/opensc-devel
