Hi Alon, > You can first try out my solutions: > > PKCS#11 support with OpenSSH > http://alon.barlev.googlepages.com/openssh-pkcs11
This is great, and I understand the use case. Its much harder to re-write openssh using a PKCS#11 interface than to provide an engine that calls PKCS#11. This still shouldn't require multiple providers or necessarily multiple slots. > PKCS#11 support with OpenVPN > http://openvpn.net/download.html#beta > > PKCS#11 for GnuPG > http://gnupg-pkcs11.sourceforge.net/ > > PKCS#11 for QCA using PSI > http://forum.psi-im.org/thread/4630 > > PKCS#11 for GnuTLS > http://alon.barlev.googlepages.com/gnutls-pkcs11 > > I have few other... But I think you can understand why the open source > community needs code reuse in order to integrate hardware cryptography > based on PKCS#11 into applications. Sorry, I didn't look through each one. Code reuse is great, I just don't see why writing to a new interface helps that. > Many users already enjoy these solutions, I thought that eCryptfs > users can also benefit from my help. Of course, help is not the issue at all... Kent -- Kent Yoder IBM LTC Security Dev. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ eCryptfs-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ecryptfs-devel
