Adam R. B. Jack wrote:
Does this answer the question?
http://lsd.student.utwente.nl/gump/jce/jce_details.html#Outputs
As I understand the JCE configuration, someone needs to install the
correct bouncycastle jar in the correct directory, and then update
jce.xml to correctly reflect the new
> As an aside - can someone tell me what the latest available bouncycastle
> jar is on lsd?
Does this answer the question?
http://lsd.student.utwente.nl/gump/jce/jce_details.html#Outputs
If not, and if we can add more to Gump for remote debugging, please provide
feedback.
regards
Adam
Stefan,
Many many thanks for all your help - we had a successful run for
xml-security last night. So now I'll start updating everything to the
latest versions.
As an aside - can someone tell me what the latest available bouncycastle
jar is on lsd?
Cheers,
Berin
Berin Lautenbach wrot
Ahhh - that makes sense. I assumed it wasn't there at all, and the
build process couldn't write to the directory (it automatically tries to
download the JAR).
Trying to diagnose remotely is difficult.
I use 13-116 here with JDK 1.4 and it works fine, which is the other
reason I reverted. I'm
On 5 Mar 2004, <[EMAIL PROTECTED]> wrote:
> Reverting to jdk1.3 JCE without boot option
We are using JDK 1.4, won't this cause problems? In particular, I'm
not sure the jar is properly signed.
Last night's build on LSD failed as the file permissions on the jar
have been wrong by accident (fix
blautenb2004/03/05 03:15:11
Modified:project jce.xml
Log:
Reverting to jdk1.3 JCE without boot option
Revision ChangesPath
1.16 +1 -1 gump/project/jce.xml
Index: jce.xml
===
RCS file: /hom
Stefan,
Looks like more failures with xml-security.
As an aside, I've found that even the beta JDK1.5 provider may not
support everything we need, and 1.4 definitely doesn't.
The current failure is around trying to download the BC JCE, so I have
reversed out the change around the JDK1.4 JCE to
>> Stefan,
>> Unfortunately I don't think we can use the JDK1.4 provider, as it
>> doesn't implement some of the padding we need (thus the errors from
>> the previous builds).
>
> No, no problems with padding so far.
My experience was that the policy file is only needed if BC is not
available. I
On Tue, 02 Mar 2004, Berin Lautenbach <[EMAIL PROTECTED]> wrote:
> Stefan,
>
> Co-incidental :>.
Absolutely since I just now have removed the provider from the
bootclasspath and things are improving.
I've just now received
[junit] java.lang.SecurityException: Unsupported keysize or algorit
bodewig 2004/03/02 04:05:21
Modified:project jce.xml
Log:
provider must not be on the boot classpath
Revision ChangesPath
1.15 +1 -1 gump/project/jce.xml
Index: jce.xml
===
RCS file: /home
Stefan,
Co-incidental :>. I was just looking at this.
Unfortunately I don't think we can use the JDK1.4 provider, as it
doesn't implement some of the padding we need (thus the errors from the
previous builds).
I did some tracking - and the problem from the previous builds is that
if the BC J
bodewig 2004/03/02 03:27:31
Modified:project jce.xml xml-security.xml
Log:
Use the JDK 1.4 provider instead of the JDK 1.3 JCE
Revision ChangesPath
1.14 +1 -1 gump/project/jce.xml
Index: jce.xml
===
12 matches
Mail list logo
