The extreme ease with which Java .class files can be reconstructed into Java sources that closely resemble the originals has a lot to do with Java byte-code design goals and trade-offs.

One proposal would restrict Java APIs to maintain the strong encapsulation that assures the integrity of code and data, while a second would introduce a Key Encapsulation Mechanism API.

The java version is using TripleDES encryption in CBC mode with PKCS5 padding. From what I've read and seen on the web, mcrypt with PHP does not support PKCS5 padding.

This is for a school project and they're forcing us to use JDK1.3.1 and the cryptix.org JCE implementation.<BR><BR>Any help would be greatly appreciated. I've run into a wall on this one.