From: Thomas W. <tc...@to...> - 2007-07-12 08:42:00
|
Hello, > If I start the Trusted Core Services Daemon tcsd of the TrouSerS TSS, I get > another error message. > ----------------------------------------------------------- > 23:50:18:338 [INFO] CommonSettings::getTssFactory (39): TrouSerS and/or > jTSS Wrapper not found. Trying IAIK jTSS. > 23:50:18:406 [WARN] TcTddlLinux::open (-1): Unable to open TPM device > file /dev/tpm. > Reason: /dev/tpm (Device or resource busy) > > 23:50:18:407 [ERROR] TcTcsi::<clinit> (-1): TCS startup failed. >[...] > additional info: Unable to open TPM device file /dev/tpm. > Reason: /dev/tpm (Device or resource busy) If you are running TrouSerS (tcsd), it exclusively opens the TPM device file. Therefore jTSS (full Java TSS) can not access the device and you get the TCS startup error message. By default, jTpmTools first try to use TrouSerS via jTSS Wrapper. If that fails (as in the case above) it falls back to jTSS (which in turn fails because TrouSerS Daemon (tcsd) is blocking the TPM device). So far so good. Question now is why jTSS Wrapper does not work for you. jTpmTools documentation says: "The jTpmTools expect the additional IAIK/OpenTC jTSS Wrapper libraries to be located in the ext_libs subfolder. jTpmTools requires a IAIK/OpenTC jTSS Wrapper of the 0.3.x series, the 0.2.x series is not compatible!" In other words you have to copy (or symlink) iaik_jtss_wrapper.jar, iaik_jtss_wrapper_swig.jar and libtspiwrapper.so into the ext_libs folder. > In addition when using the jTSS I am not able to create AIK key I get the > following Exception. > [...] > Exception in thread "main" java.lang.NoClassDefFoundError: > iaik/x509/X509ExtensionException > at iaik.tc.apps.jtt.aik.AikCreate.execute(AikCreate.java:258) > at iaik.tc.utils.cmdline.SubCommand.run (SubCommand.java:69) > at iaik.tc.utils.cmdline.SubCommandParser.parse( > SubCommandParser.java:41) > at iaik.tc.apps.JTpmTools.main(JTpmTools.java:110) Please double check that you have IAIK JCE, TcCert and friends installed correctly. Regards, -- Thomas Winkler e-mail: tc...@to... |