From: Ronald T. <ron...@ia...> - 2011-01-25 13:26:55
|
Hi, Tom is right, and I'll just add some explanation to the discussion. Remember that a TSS such as jTSS consists of TSP and TCS layers, connected by some binding interface (local := reliance on the Java class loader or soap := XML over TCP/IP). You alwayse need a single TCS per hardware TPM, because the TCS has been designed to be a software abstraction and management layer of the chip. There can only be one TCS instance per singleton TPM. You can however run arbitrarily many TCS daemons on your system, if you assign them separate TPMs, storage directories and SOAP port numbers. In each of your applications, you can also load just one instance of the TSP library. However, you can create as many TPMContexts and connections to the TCS layer there as you like. You can also connect those contextes to different TCS services (using the hotfix I sent you). Note that you must use SOAP bindings for this. Thus you should be able to use different TPMs at the same time. Still, this has not been tested and side effects might occur. hth, Ronald On 01/25/2011 12:36 PM, Thomas Winkler wrote: >> I just noticed that even iaik.tc.tss.impl.java.tddl.TcTddl is >> implemented as singleton. Doesn't that make it impossible to create >> different TPM connections inside the same runtime JVM? > I still have not understood why you need several TCS instances in one single > JVM. I can understand that you might need several connections to different TCS > instances running in different JVMs. From your application's point of view this > does not look very different than the (hypothetical) case of multiple > connections to different TCS instances in the same VM. And that's something > that should be doable with jTSS without much effort. -- Dipl.-Ing. Ronald Tögl phone +43 316/873-5502 Secure and Correct Systems fax +43 316/873-5520 IAIK ron...@ia... Graz University of Technology http://www.iaik.tugraz.at |