|
From: Ronald T. <ron...@ia...> - 2011-01-24 12:27:46
|
Hi Sebastian,
From the architectural point of view, you should use separate instances
of the TCS service for each TPM instance. You can then discern them by
using different port numbers for the SOAP interface.
Practically, there is a bug in the Soap Binding implementation so that
it will ignore your selection in TCIContext.connect("<hostname>") and
will just use the settings from the .ini file. :-/
Do you need to call to several TPMs from the same JVM process/Class
Loader hierarchy? Else, you can just use one app for each TPM and set it
in the ini file.
hth,
Ronald
On 01/24/2011 01:14 PM, Sebastian Luft wrote:
> Hi List,
> I'm using a custom written TDDL implementation to be able to connect
> to multiple software TPM instances. I am currently using the
> TcTcsProperties class to set an instance ID property which the TDDL
> can read out to know which TPM to connect to. The problem is that the
> TcTcsProperties class is designed as singleton so I cannot use it to
> manage multiple TDDL connections.
> Is jTSS even designed to work with multiple TPM devices (software
> emulators)? Any Idea on how to be able to pass an ID over to TCS so it
> knows which TPM device to talk to?
> Kind regards, Sebastian.
--
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
|