Hello Make sure you enabled this token's compilation by calling ./configure with --enable-tpmtok.
Since we won't necessarily find all tokens in the platform we're dealing with, most of them are not compiled by default. ./configure --help will give a list of, other than the usual ones, the tokens that are implemented and their default compilation state (i.e. default=disabled). Which distro is it? It strongly looks that the token wasn't built in this package... Unfortunately the pkcs11_startup script isn't linked to the those configure options (yes, a nice-to-have to take not, thanks :-), and will indeed look for all tokens, regardless if they were built or not. Thanks, Rajiv Andrade IBM LTC Security Development On Tue, 2009-09-08 at 18:43 -0300, Klaus Heinrich Kiwi wrote: > On 09/06/2009 05:29 PM, Marc Kaeser wrote: > > Hello! > > > > Thanks, I've seen the other thread, and I'm very interested in it :-) I > > wonder how Subrata Mazumdar managed to load that module - maybe other > > versions? > > But I must say my problem's still of lower class than loading the module > > into NSS for the moment. I've found out the problem of my package. Using > > strace, I saw that pkcs11_startup looked for soft links which pointed to > > nothing, the files were missing. After that I removed the package, and > > tried to build opencryptoki again, from the source found on sourceforge, > > cause I thought the libs would all be included, there. But now the lib > > libpkcs11_tpm.so is missing, and therefore pkcs11_startup fails to > > create the settings for pkcsslotd, and I think that's the problem why I > > can't see the tpm-token with pkcsconf -s. I don't know where to find it, > > but I hope I'll find out soon :) > > > > Marc > (moving to opencryptoki-tech) > > This is a known issue which we haven't had the time to properly fix yet. > > pkcs11_startup blindly looks for files in <prefix>/lib to check what > tokens are present (well, sometimes it also checks for loaded modules > and such). > > Thing is, sometimes opencryptoki install those files in <prefix>/lib64. > When pkcs11_startup can't find the stdll libraries, it fails to > configure the token. > > The ugly hack we sometimes do in distro packages is to create empty > files in <prefix>/lib to pretend to be those libraries, when in fact > they are places in <prefix>/lib64. This may not work so well when > building from source. > > Are you using pre-built binaries for some distribution? Can you give us > more details? > > ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Opencryptoki-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opencryptoki-tech
