Re: [Trustedjava-support] Problems with jTpmTools and/or JTSS

[Till B. <ti...@on...>]

Hello,

I just tried using the wrapper and TrouSerS and now it works. So I guess
there is a problem inside JTSS or something like that...

On 7/4/07, Thomas Winkler <tc...@to...> wrote:
>
> Hello,
>
> >  $ sh jtt.sh take_owner -o till
> [...]
> > LOG_DEBUG TSPI ../tcsd_api/clntside.c:102 Sending TSP packet to host
> > localhost.
> > LOG_DEBUG TSPI ../tcsd_api/clntside.c:118 Connecting to 127.0.0.1
> > LOG_ERR TSPI ../tcsd_api/clntside.c:121 ERROR: connect: Connection
> refused
> > LOG_ERR TSPI ../tcsd_api/tcstp.c:247 ERROR: Failed to send packet
> > 18:18:04:207 [INFO] CommonSettings::getTssFactory (39): TrouSerS and/or
> > jTSS Wrapper not found. Trying IAIK jTSS.
> > 18:18:04:405 [INFO] TcTcsi::<clinit> (-1):      Unable to open TCS
> > configuration file for system persistent storage information. Disabling
> > system persistent storage.
> > 18:18:04:453 [INFO] CommonSettings::getTssFactory (47): IAIK jTSS found.
> > Using local bindings...
> > 18:18:17:680 [INFO] TakeOwnership::execute (82):        TakeOwnership
> > succeeded
>
> The above trace is telling me that you are using the full jTSS and not the
> wrapper. Taking the ownership succeeded. So far so good.
>
>
>
> > $ sh jtt.sh read_pubek -o till
> [...]
> > 18:18:37:943 [INFO] CommonSettings::getTssFactory (47): IAIK jTSS found.
> > Using local bindings...
> > iaik.tc.tss.api.exceptions.tcs.TcTpmException:
> >
> > TSS Error:
> > error layer:                0x00 (TPM)
> > error code (without layer): 0x01
> > error code (full):          0x01
> > error message: Authentication failed
>
> This indeed is strange. Since you have supplied the same password as when
> taking ownership this should not fail. Back at the IAIK labs we had a
> machine
> with an STM 1.2 TPM and as far as I can recall everything worked as
> expected
> on that machine.
>
> bye,
> --
> Thomas Winkler
> e-mail: tc...@to...
>



-- 
Regards
  Till

**********************************************
      Der Benutzer ist eine nicht zu
  tolerierende Quelle der Unsicherheit
**********************************************