On 25.02.2007, at 20:16, Henryk Plötz wrote:
Possible improvements:
- provide a ISO 7816-4 API to use select_file() instead of hex
notation "00A4"
- provide a VerifyPin() instead of direct call to SCardControl()
That is not easy and it would be best to create an opensc interface
for that purpose in order to not write Yet Another Library Against
Smartcard Quirks and duplicate a lot of functionality.
OpenSC python bindings
I like the idea.
I have been working with M2Crypto for a while (OpenSSL SWIG bindings)
and created some patches and while doing that thought about writing
SWIG wrappers
for opensc PKCS15 layer at some point.
Also, combining the selection of python and other language and
library integrations
into a wiki page would definitely be a benefit to everybody.
We currently have:
perl pcsc bindings
python pcsc bindings
openssl pkcs11 bridge - pkcs11 engine
python pkcs11 bridge - pykcs11
python openssl bridge - m2crypto
... what else ?
I'm sure there are many python programmers out there who would
benefit from clear and functional interfaces
to develop cool new stuff. Sorting out the interfaces and maybe
adding some new features to these libraries might enable many people
to play with new ideas.
For example creating a web server using a keypair on smart card for
SSL connections via opensc-pkcs11/pkcs11_engine/m2crypto/twisted
(possible, patches are out there)
Or using m2crypto with the same software stack with urllib2 and all
other python libraries using urllib2 (almost everything)
If other python users would speak up what they are doing or would
like to do we could figure out some patterns maybe.
m.
--
Martin Paljak
_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel
