lets test first, if it doesn't work...
in opensc.conf I see we have max_send_size and max_read_size
already, but only in reader section. but the ctx.c code looks
generic, so we could copy that example setting to reader openct
section as well?
no further code changes are necessary to test lower
Andrey Jivsov wrote:
First, it is unclear what number 248 represents. The lowest common
denominator? T=1 adds 4 bytes of headers+checksum, which gives us 252:
still smaller than 255 or 254 that one might expect to see...
if I remember the statistic ludovic did, all readers support at least
--On Monday, November 13, 2006 09:23:06 AM +0100 Andreas Jellinghaus
[EMAIL PROTECTED] wrote:
I have no clue: would that restrict them? i.e. take functionality away?
or would opensc only split one command into several smaller ones and thus
preserve functionality, but add more communication
Andreas Jellinghaus wrote:
+/* need to limit to 248 */
+if (card-max_send_size 248)
+card-max_send_size = 248;
+if (card-max_recv_size 248)
+card-max_recv_size = 248;
+
+
can we put something like this in the generic code for
all cards and drivers? or in the
Andreas Jellinghaus wrote:
Nils Larsch wrote:
well, it depends on whether this is card 'feature' or a limitation
of the card reader.
Card reader - the same card works fine in some readers, not in others.
unfortunatly it is not even detectable via the driver - some ccid
readers work
Andreas Jellinghaus wrote:
lets test first, if it doesn't work...
test what ? If we globally restrict the buffer size we certainly
will have problems with some tokens (etokens pro with 2048 bit keys,
note: cardos m4.2 doesn't have a GET RESPONSE command = every byte
that doesn't fit into the
Nils Larsch wrote:
I already tested 2048 bit rsa signatures with an etoken pro
using openct so at least it seems to work for cardos.
it also works with openct + ccid driver + cryptoflex 32k egate.
but: only for some readers. for example all scm readers won't
work.
Regards, Andreas
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
+ /* need to limit to 248 */
+ if (card-max_send_size 248)
+ card-max_send_size = 248;
+ if (card-max_recv_size 248)
+ card-max_recv_size = 248;
+
+
can we put something like this in the generic code for
all cards and drivers? or in the openct
Nils Larsch wrote:
well, it depends on whether this is card 'feature' or a limitation
of the card reader.
Card reader - the same card works fine in some readers, not in others.
unfortunatly it is not even detectable via the driver - some ccid
readers work fine, some don't.
If it's property
On Sat, Nov 11, 2006 at 05:53:00PM +0100, Andreas Jellinghaus wrote:
if limiting all readers to 248 bytes doesn't hurt anyone, then this
is the best way from my point of view.
I would like to avoid that if possible..
Also I'd like to make this a config file option. I guess that some
11 matches
Mail list logo
