Hi Ludovic, how tied is the ccid reader to supporting ccid only? or could you implement other protocols in it as well?
in theory I'm all for using the best software available, and at least once pinpad support is required that is pcscd with your ccid driver and not openct. but keeping openct around with or without ccid driver, or having some other drivers around to implement non-ccid drivers all ends up with the same result: lots of common functionality in several places. one of the first drivers in openct where those for aladdin etoken pro, rainbow ikey 2k, 3k and similar. the difference between those is lots of s/etoken/ikey2k/g and maybe 10 real lines of code. noone wants to maintain several copies of t=1, we already have more than we need (openct, ccid, other drivers, scez, ...) and also maintaining the framework around the driver core would be lots of identical code. is there any way we can obsolete openct by having a driver for pcscd, that supports (almost?) every reader openct supports? for example adding drivers to ccid, or building several drivers from one common source? Regards, Andreas _______________________________________________ opensc-devel mailing list [email protected] http://www.opensc-project.org/mailman/listinfo/opensc-devel
