You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@gump.apache.org by Berin Lautenbach <be...@wingsofhermes.org> on 2004/03/01 11:57:58 UTC
Failures in xml-security
Peoples,
Could someone check if the bouncycastle JCE has been installed on lsd?
The project is :
http://lsd.student.utwente.nl/gump/jce/jce.html
and it looks like it's never been in place? I *think* this is what is
causing xml-security to fail as it's defaulting to the Sun JCE which
doesn't have all the algorithms we need. (Or rather it does, but we
don't have all the configs to use it.)
http://lsd.student.utwente.nl/gump/xml-security/gump_work/build_xml-security_xml-security.html
With thanks!
(BTW - Am assuming I can't do this myself?)
Cheers,
Berin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Failures in xml-security
Posted by Berin Lautenbach <be...@wingsofhermes.org>.
> On Mon, 01 Mar 2004, Stefan Bodewig <bo...@apache.org> wrote:
> If I do so for the latest version, I get a different type of error
> message
>
> [junit] org.apache.xml.security.encryption.XMLEncryptionException:
> Padding: ISO10126PADDING not implemented [junit] Original Exception
> was javax.crypto.NoSuchPaddingException: Padding: ISO10126PADDING
> not implemented [junit] at
> org.apache.xml.security.encryption.XMLCipher.getInstance(XMLCipher.java:285)>
> but it looks as if bouncycastle doesn't get used at all.
Yup - thus my original question :>. The SunJCE only supports
PKCS5Padding, which is not quite what we need (it's fussy in places that
break the interop testing for xml-security).
But what I don't understand is why it (the SunJCE) is getting called. I
am running a 1.4 JRE and still getting BC called for all crypt. I
actually have to explictly remove BC from the CLASSPATH and update some
configurations inside xml-security, to get these errors.
> If I only use the provider jar and nothing else, I again get another
> error (something about not being able to find provider "BC" or not
> being able to verify it).
>
> To me it looks as if we'd have to install things to use bouncycastle
> with JDK 1.4 anyway, at least the unrestricted policy file has to be
> installed. I'd be glad if anybody with a better JCE background than I
> have could help out here.
That's got me confused as well. If the policy files are not installed,
then we should be getting errors about unsupported key lengths long before
we get a padding error - or at least that's my experience.
Let me play around on a test system and see if I can replicate the problem
on a test system here.
Cheers,
Berin
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Failures in xml-security
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 01 Mar 2004, Stefan Bodewig <bo...@apache.org> wrote:
> On Mon, 01 Mar 2004, Berin Lautenbach <be...@wingsofhermes.org>
> wrote:
>
>> Could someone check if the bouncycastle JCE has been installed on
>> lsd?
>
> Yes, version 1.1.6. This may be too old for xml-security's needs.
> I'll look into upgrading it just now.
Hmm, we've been using bouncycastle's cleanroom JCE for 1.3, actually.
If I do so for the latest version, I get a different type of error
message
[junit] org.apache.xml.security.encryption.XMLEncryptionException: Padding: ISO10126PADDING not implemented
[junit] Original Exception was javax.crypto.NoSuchPaddingException: Padding: ISO10126PADDING not implemented
[junit] at org.apache.xml.security.encryption.XMLCipher.getInstance(XMLCipher.java:285)
but it looks as if bouncycastle doesn't get used at all.
If I only use the provider jar and nothing else, I again get another
error (something about not being able to find provider "BC" or not
being able to verify it).
To me it looks as if we'd have to install things to use bouncycastle
with JDK 1.4 anyway, at least the unrestricted policy file has to be
installed. I'd be glad if anybody with a better JCE background than I
have could help out here.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Failures in xml-security
Posted by Stefan Bodewig <bo...@apache.org>.
On Mon, 01 Mar 2004, Berin Lautenbach <be...@wingsofhermes.org> wrote:
> Could someone check if the bouncycastle JCE has been installed on
> lsd?
Yes, version 1.1.6. This may be too old for xml-security's needs.
I'll look into upgrading it just now.
There doesn't seem to be a clean room JCE for JDK 1.4 anymore, I check
whether it works by just adding the providers, but I doubt so. If it
fails, I'll try 1.2.1 instead, which seems to be tha last release with
a clean room JCE.
> (BTW - Am assuming I can't do this myself?)
Since bouncycastle doesn't get built from sources but uses an
installed package, this requires an account on the machines running
Gump.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org