From: Davide V. <dav...@po...> - 2010-03-01 17:07:36
|
On Mon, Mar 1, 2010 at 3:30 PM, Ronald Tögl <ron...@ia...> wrote: > Davide Vernizzi wrote: > >>>> Do you have any other process which bind at the 30003? >>> >>> As to be expected, I did have the jTSS service running. :-) >>> After freeing the socket, trousers works fine. It would be a good thing >>> to have the port number configurable, right? >> >> Yes, you are right (we are actually working on this right now)... but >> then also applications must change the port number accordingly (maybe by >> specifying a URI in the Tspi_Context_Connect). > >> BTW, under Windows (Vista & 7) TrouSerS is built to use the TBS, which >> "multiplexes" the TPM and allows for concurrent TSS. We successfully >> tested TrouSerS in parallel with IFX's stack, and it would be nice to >> test also with jTSS. Does jTSS have configurable port number? If yes, >> could you test if they can coexist? > > I just did some testing and decided to change the jTSS default port to > 30004. This should help avoid collisions. It will be included in the > upcoming release of jTSS. > > With this change I can confirm that jTSS and Trousers coexist happily on a > single TBS-multiplexed TPM. Cool. Many thanks. Best. -- Davide |