trustedjava-support

[Trustedjava-support] jTpmTools "XKMS-commands" error due to classpath

[Nektarios I. <ine...@gm...>]

Hello,

When I try to run the command

./jtt.sh xkms_ekcert_create -o theBIGsecret --ekfile ek.cert --auth xxxxxx

I get
--------------------------------------------------------------------------------------------------------------------------------------
11:49:34:385 [INFO] CommonSettings::getTssFactory (37): TrouSerS TSS found.
Using JNI bindings...
***
***
***
***
Public EK extracted (MD5:b7c12929370ef4bce4585cea772be146)
***
***
***
***

sending RegisterRequest...
WARNING: No Version of Xerces found, please check your classpath, defaulting
to DOM LEVEL 3
11:49:38:059 [ERROR] XEkCreate::execute (141):  iaik.xkms.XKMSException:
signing failed: Cannot find algorithm '
http://www.w3.org/2001/10/xml-exc-c14n#' for mechanism type 'DOM'.

--------------------------------------------------------------------------------------------------------------------------------------

I was facing the same problem with XKMS's testsuite script "runtest.rb" but
after adding the path
to my "xerces.jar" file to the script's "classpath" variable fixed the
problem.

How can I do the same for jtt (so that it's XKMS-type commands can find my
"xerces. jar") ?

(I tried to add the xerces path to my $PATH variable for my terminal
sessions but this did not help)

Regards,

Nektarios

Re: [Trustedjava-support] XKMS 0.2 + Java 6

[Martin P. <Mar...@ia...>]

Nektarios Ioannides wrote:
> WARNING: No Version of Xerces found, please check your classpath, defaulting to DOM LEVEL 3
> signing failed: Cannot find algorithm 'http://www.w3.org/2001/10/xml-exc-c14n#' for mechanism type 'DOM'.

The warning is displayed by Xsect 1.11, Xsect 1.10 does not print a warning.

The underlying issue is that Java 6 contains new (partial) XMLDSIG support which
was not included in Java 5. Xsect offers full XMLDSIG+XMLENC and when using Java 6
you have to be careful with mixing both implementations/providers.

The next build of Xsect should be more robust in interaction with Java 6
provided parts, in the meantime one has to be a little careful during initialisation.

Please replace your IAIK.class in your iaik_xkms.jar with attached version.
The Xerces warning persists (because Suns bundled version of Xerces AFAIR does not
contain a version), but the signing works as expected.


HTH

-- 
Martin Pirker
IAIK, TU Graz