Re: diffie-hellman problem
On Tue, 2006-06-27 at 21:27 +1000, Raif S. Naffah wrote: > found the problem; should be able to check-in a fix within the next > 48h. Very cool! Thanks for the quick fix. Does this Sun demo now work for you? It does not throw the exception anymore, but it hangs here with 0% cpu: Shared secrets are the same Return shared secret as SecretKey object ... DES in ECB mode recovered text is same as cleartext DES in CBC mode recovered text is same as cleartext jamvm crashes on my x86_64, so I don't know if that's a cacao bug. Another thing is, it didn't fix the problem in this proprietary application I'm trying to run. I'll paste the stacktrace, maybe you have an idea: java.security.spec.InvalidKeySpecException: Unexpected OID: 1.3.14.3.2.12 at gnu.java.security.jce.sig.DSSKeyFactory.engineGeneratePublic(DSSKeyFactory.java:96) at java.security.KeyFactory.generatePublic(KeyFactory.java:219) at hox.corem.server.LicenseManagerImpl.(LicenseManagerImpl.java:89) Caused by: java.security.InvalidParameterException: Unexpected OID: 1.3.14.3.2.12 at gnu.java.security.key.dss.DSSKeyPairX509Codec.decodePublicKey(DSSKeyPairX509Codec.java:204) at gnu.java.security.jce.sig.DSSKeyFactory.engineGeneratePublic(DSSKeyFactory.java:91) ...2 more TWISTI
[Bug crypto/28192] New: Algorithm names should be case insensitive
Algorithm names should be considered to be case insensitive, yet gnu-crypto is treating them as being case sensitive. This causes a "NoSuchAlgorithmException" if the algorithm string passed does not match the exact case as the algorithm listed in gnu-crypto. I have traced the issue to gnu.java.security.Engine and its getInstance methods. These methods take the algorithm string passed to them as a key to find the algorithm class in a hashtable. Instead of using the algorithm name as a key, they hashtable needs to be iterated through each algorithm and doing a compare ignoring the case. -- Summary: Algorithm names should be case insensitive Product: classpath Version: 0.92 Status: UNCONFIRMED Severity: normal Priority: P3 Component: crypto AssignedTo: csm at gnu dot org ReportedBy: mwringe at redhat dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28192 ___ Bug-classpath mailing list Bug-classpath@gnu.org http://lists.gnu.org/mailman/listinfo/bug-classpath
[Bug crypto/28192] Algorithm names should be case insensitive
--- Comment #1 from mwringe at redhat dot com 2006-06-28 16:02 --- Created an attachment (id=11770) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11770&action=view) Patch to add algorithm name case sensitivity checking to the Engine.getInstance testcase This patch adds case sensitivity testing of the algorithm name to the gnu.testlet.java.security.Engine.getInstance test. If this test is deemed acceptable, could someone please commit it for me. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28192 ___ Bug-classpath mailing list Bug-classpath@gnu.org http://lists.gnu.org/mailman/listinfo/bug-classpath
[Bug crypto/28192] Algorithm names should be case insensitive
--- Comment #2 from mwringe at redhat dot com 2006-06-28 16:11 --- Created an attachment (id=11771) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11771&action=view) Patch that removes case sensitivity of the algorithm name in java.security.Engine This proposed patch will now allow the gnu.java.security.Engine getInstance methods to properly ignore case sensitivity of the algorithm names. This will also allow the proposed Mauve getInstance test to pass: http://gcc.gnu.org/bugzilla/attachment.cgi?id=11770 Please review and comment. Thanks, Matt Wringe -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28192 ___ Bug-classpath mailing list Bug-classpath@gnu.org http://lists.gnu.org/mailman/listinfo/bug-classpath
Re: diffie-hellman problem
Hi, On 6/28/06, Christian Thalinger <[EMAIL PROTECTED]> wrote: On Tue, 2006-06-27 at 21:27 +1000, Raif S. Naffah wrote: > found the problem; should be able to check-in a fix within the next > 48h. Very cool! Thanks for the quick fix. Does this Sun demo now work for you? It does not throw the exception anymore, but it hangs here with 0% cpu: Shared secrets are the same Return shared secret as SecretKey object ... DES in ECB mode recovered text is same as cleartext DES in CBC mode recovered text is same as cleartext jamvm crashes on my x86_64, so I don't know if that's a cacao bug. Any chance you could provide some details? Thanks, Rob. TWISTI
Re: diffie-hellman problem
On Wed, 2006-06-28 at 17:27 +0100, Robert Lougher wrote: > Any chance you could provide some details? Yeah, sorry. Ok, here we go: This is jamvm-1.4.3 on x86_64-linux. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1241594208 (LWP 25793)] objectLock (obj=0x2ade337c0008) at lock.c:314 314 if((entering = ATOMIC_READ(&mon->entering)) == UN_USED) (gdb) bt #0 objectLock (obj=0x2ade337c0008) at lock.c:314 #1 0x00419f5e in threadStart (arg=) at thread.c:315 #2 0x2ade33399b1c in start_thread () from /lib/libpthread.so.0 #3 0x2ade335759c2 in clone () from /lib/libc.so.6 #4 0x in ?? () TWISTI
