Re: [Trustedjava-support] (Windows) Running the TCS daemon directly without installing the service?

[Matthew G. <mat...@gm...>]

Looking at the source briefly, I pulled out the jTssTddlVista.dll and threw
them in the lib paths without much success. It is odd, this may be related
to the VC redist, as the relevant JAR is in the path, and I am unsure why
it can't load. I'll make sure my vc redist is working and try again.


On Tue, Jul 1, 2014 at 4:08 PM, Matthew Galligan <mat...@gm...
> wrote:

> Hello,
>
> I have a use case where I need to do a one-time encryption of something on
> a lot of workstations (2000+) and was hoping to run the TCS daemon directly
> from command line for this so that I could avoid permanently installing
> jTSS on all of these machines. I periodically boot to another partition on
> these machines that has jTSS installed.
>
> In Windows, I have run the following (wild guess so probably pretty
> wrong):
>
> java -cp
> .;C:\PROGRA~1\jTSS\soap\..\lib\iaik_jtss_tsp_tests.jar;C:\PROGRA~1\jTSS\soap\..\lib\iaik_jtss_tsp_soap.jar;C:\PROGRA~1\jTSS\soap\..\lib\iaik_jtss_tsp.jar;C:\PROGRA~1\jTSS\soap\..\lib\iaik_jtss_tcs_soap.jar;C:\PROGRA~1\jTSS\soap\..\lib\iaik_jtss_tcs.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\hsqldbmin.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\junit.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\xerces.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\wsdl4j-1.5.1.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\saaj.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\mail.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\log4j-1.2.8.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\jaxrpc.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\commons-logging-1.0.4.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\commons-discovery-0.2.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\commons-daemon.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\axis.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\axis-ant.jar;C:\PROGRA~1\jTSS\soap\..\ext_libs\activation.jar
> -Djtss.tsp.ini.file=C:\PROGRA~1\jTSS\soap\..\lib\ini\jtss_tsp.ini
> -Djtss.tcs.ini.file=C:\PROGRA~1\jTSS\soap\..\lib\ini\jtss_tcs.ini
> iaik.tc.tss.impl.java.tcs.soapservice.server.StartAxisServerWindows
>
> I copied the classpath out of the service properties and I get the
> following output:
>
> 10:23:08:434 [INFO] StartAxisServerWindows::setupServer (81):
> Initializing the
>  AXIS server
> 10:23:08:512 [INFO] StartAxisServerWindows::setupServer (87):   AXIS
> server succ
> essfully initialized
> 10:23:08:730 [INFO] StartAxisServerWindows::startServer (98):   Try to
> start the
>  AXIS server
> 10:23:08:730 [INFO] StartAxisServerWindows::startServer (101):  AXIS
> server succ
> essfully started
> - starting up SimpleAxisServer on port 30004 (C:\Program Files\jTSS\lib)
>
>
> However, when I run jtt I get the following:
>   ---------------------
>    IAIK Java TPM Tools
>   ---------------------
> 10:32:16:878 [ERROR] TcTcsBindingSoap::connect (116):   There seems no TCS
> runni
> ng
> 10:32:16:893 [ERROR] TcTcsBindingSoap::connect (116):   There seems no TCS
> runni
> ng
> iaik.tc.tss.api.exceptions.tsp.TcTspException:
>
> TSS Error:
> error layer:                0x3000 (TSP)
> error code (without layer): 0x0103
> error code (full):          0x3103
> error message: Core Service connection failed.
>
>         at
> iaik.tc.tss.impl.java.tsp.tcsbinding.soapservice.TcTcsBindingSoap.con
> nect(TcTcsBindingSoap.java:117)
>         at
> iaik.tc.tss.impl.java.tsp.internal.TcTspInternal.TspContextConnect_In
> ternal(TcTspInternal.java:368)
>         at iaik.tc.tss.impl.java.tsp.TcContext.connect(TcContext.java:174)
>         at iaik.tc.apps.jtt.tpm.TpmVersion.execute(TpmVersion.java:68)
>         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:224)
>
> I've noticed the same behavior when running the daemon on linux.
>