On 10/9/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote: > All the other notes based on this assumption, I will be happy to > explain more if you like.
You can first try out my solutions: PKCS#11 support with OpenSSH http://alon.barlev.googlepages.com/openssh-pkcs11 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. Many users already enjoy these solutions, I thought that eCryptfs users can also benefit from my help. Users reports working providers and I keep track of it, this is a partial list: http://www.opensc-project.org/pkcs11-helper/wiki/WorkingProviders Best Regards, Alon Bar-Lev. ------------------------------------------------------------------------- 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
