On Wed, Oct 10, 2007 at 10:28:50PM +0200, Alon Bar-Lev wrote: > But it seems we have understand the the official differently, do you > mean "binary rpm" as official and source tarball as not?
The source tarball that we post on the SourceForge site is the "official" distribution of ecryptfs-utils. > I don't understand openCryptoki is a provider (as far as I know) and > OpenSSL engine. > Why will you consider linking against it? Linking against a specific > provider is not the PKCS#11 way, as the user cannot use provider he > chooses. A generic "pkcs11" key module, if one ever gets implemented in the future, will dlopen() a library and then make PKCS#11 API calls to that library. For deployments on SLES and RHEL, the configuration file that specifies the library will point to a library that implements the PKCS#11 interface, and any PKCS#11 implementation shipping in SLES and RHEL will be appropriate to put in that configuration file. Mike
pgpif59mfJ1Mi.pgp
Description: PGP signature
------------------------------------------------------------------------- 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
