I agree to these limitations and would love to get rid of them by having an open and pkcs#11 compatible implementation. But we do not have the capacity and experience to develop such a smart card right now. Therefore any support to develop such an open smart card implementation is more than welcome!
Alon Bar-Lev schrieb: > This is not full PKCS#11 provider and has many limitations of > implementation and many other inherited from OpenPGP specification. > > Examples: > 1. Limitation of 1024 RSA key size. > 2. Requirement to hold the certificate within gpgsm and not on card. > 3. Complex communication between > application->provider->gpgsm->gpg-agent->scdaemon. > 4. Partial implementation of PKCS#11, one bug I remember is fork() compliant. > Others that I already forgot. > > Alon. > > On 10/15/08, Jan Suhr <[EMAIL PROTECTED]> wrote: >> Hi Alon! Currently I am testing your pkcs#11 extension for gnupg. An >> pkcs#11 compatible open source implementation of a smart card or USB >> stick is something that we are planning for v2 in the future. >> >> Alon Bar-Lev schrieb: >> >>> Best is develop PKCS#11 provider and not OpenPGP specific. >> > As PKCS#11 is the interface applications use. >> > You will be able to use GPG using [1] if you like without more effort. >> > >> > Alon. >> > >> > [1] http://gnupg-pkcs11.sourceforge.net/ >> > >> > On 10/15/08, Jan Suhr <[EMAIL PROTECTED]> wrote: >> >> Hi! >> >> Currently we are developing an USB stick based on the OpenPGP smart card >> >> as an open source project. This is basically a simple smart card adapter >> >> based on the IC FT2232D (http://www.ftdichip.com/Products/FT2232C.htm). >> >> Linux includes modules to communicate with the FT2232 in general but not >> >> specifically for its usage as a smart card adapter. Also other open >> >> source libraries exist for this chip >> >> (http://www.intra2net.com/de/produkte/opensource/ftdi/). >> >> >> >> While the hardware is not any problem we are wondering about the >> >> development of an appropriate software driver. Which features and which >> >> specifications such a driver would have to fulfill? What is the average >> >> effort to develop such a driver? Is there any documentation to follow or >> >> is it possible to get any support by the community? >> >> >> >> Thanks! >> >> _______________________________________________ >> >> opensc-devel mailing list >> >> opensc-devel@lists.opensc-project.org >> >> http://www.opensc-project.org/mailman/listinfo/opensc-devel >> >> >> > >> >> >> >> -- >> Jan Suhr >> German Privacy Foundation e.V. https://www.privacyfoundation.de/ >> OpenPGP key: http://user.cs.tu-berlin.de/~jansuhr/jansuhr.asc >> Anonymous e-mail: https://www.awxcnx.de/jansuhr.msg >> > -- Jan Suhr German Privacy Foundation e.V. https://www.privacyfoundation.de/ OpenPGP key: http://user.cs.tu-berlin.de/~jansuhr/jansuhr.asc Anonymous e-mail: https://www.awxcnx.de/jansuhr.msg _______________________________________________ opensc-devel mailing list opensc-devel@lists.opensc-project.org http://www.opensc-project.org/mailman/listinfo/opensc-devel
