Re: [opensc-devel] Code for ePass3000 accomplished

Hi Andreas, Andreas Jellinghaus wrote: > I commited your patch, added your name to the list of Authors > on the wiki and started a wiki page here: > https://www.opensc-project.org/opensc/wiki/ePass3000 > once you registered some username and password, you can login and > edit this page. please pro

Re: [opensc-devel] gemsafeV1 assumes key_ref is always 3 - Ticket #179

thanks douglas, I applied your patch to trunk. Regards, Andreas ___ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel

Re: [opensc-devel] Code for ePass3000 accomplished

Hi Weitao, thanks, I commited your patch, added your name to the list of Authors on the wiki and started a wiki page here: https://www.opensc-project.org/opensc/wiki/ePass3000 once you registered some username and password, you can login and edit this page. please prove-read the page and improve

[opensc-devel] gemsafeV1 assumes key_ref is always 3 - Ticket #179

I have submitted ticket #179 with an attached patch to pkcs15-gemsafeV1.c after discussing the issue with the module's author, David Mattes. I would hope that this patch could be applied soon so it will be in 0.11.5. The pkcs15-gemsafeV1.c code assumes that the key_ref is always 3. But that is n

Re: [opensc-devel] [PATCH 2/3] libp11: API change: change id_len from int to size_t

Andreas Jellinghaus wrote: > > can you resend this patch as attachment? > your mailer broke the long lines I guess, doesn't apply :( Strange, I think that I switched normal formatting to preformatted text. Anyway, it's attached now. Please let me know, whether API change will be accepted upstre