Java - Encryption Problem

MRMadhav · 05-19-2006, 01:12 AM

Hi i have been using an encryption algorithm for more than one month now and it has been working perfectly until today! Suddenly everything has stopped working and by trying to corner the problem i figured out that it was this line that was the problem :

Code:

SecretKey key = SecretKeyFactory.getInstance("PBEWithMD5AndDES").generateSecret(keySpec);

I get this exception from this line:

Code:

java.security.NoSuchAlgorithmException: Algorithm PBEWithMD5AndDES not available

Can someone tell me how this suddenly stopped working and how to correct this?

iuaui · 05-19-2006, 03:13 AM

Hi,

are you by any chance using IBM's WebSphere? If you are, look at this:

http://www-1.ibm.com/support/docview...id=swg21236118

MRMadhav · 05-19-2006, 04:26 AM

No am not using Any of ibm's cryptography extensions

iuaui · 05-19-2006, 04:31 AM

Well, that was just a wild guess. The date was so convenient for your problem.

MRMadhav · 05-19-2006, 04:32 AM

I am using sun's cryptography extensions. here are the first few lines in the Manifest file:

Manifest-Version: 1.0
Created-By: 1.5.0 (Sun Microsystems Inc.)
Specification-Version: 1.4
Specification-Vendor: Sun Microsystems, Inc.
Implementation-Vendor-Id: com.sun
Extension-Name: javax.crypto
Implementation-Version: 1.4
Implementation-Vendor: Sun Microsystems, Inc.

I hope that this one doesn't have any problem?

MRMadhav · 05-19-2006, 04:33 AM

Yeh when i checked the page i, too found it strange, so i went and checked the jar files!

MRMadhav · 05-19-2006, 07:20 AM

Ok, That one is realy wierd! I openned up another workspace which use the same encryption class and in the same manner and it worked over there! Now that is very Disturbing! Whats the problem with my Machine?

MRMadhav · 05-19-2006, 07:32 AM

Finally, the problem is not with the application it is with eclipse! I don't know why the application would get this error when launching within eclipse but would work just fine when run with the command line, yet i am using the same runtime environment and there was not this problem till today. Must i change a certain configuration in eclipse to make it work?