Thanks Vishal. Looks like that is the problem. Not solved yet but I'm working on it.
Dominik > >Vishal, > > > >Thanks for your answer. I upgraded to the lastet Bouncy Castle jar > >(bc-jce-jdk13-123.jar). Nothing changed, same exception (ISO10126PADDING > not > >implemented). > > > >The bc-jar file is located in jre_home/lib/endorsed. /lib/ext doesn't > work > >as well as in the jdk_home dir. > > > I think that's the problem. The encrypt sample works for me with JDK > 1.4.2_04 even without a bc provider jar. You probably have to get the > /lib/ext directory in your classpath somehow, so that atleast the > sunjce_provider can get picked up. I think currently none of the jce > provider jars are getting picked for you. > > Vishal > > > I don't know why. But the jar is found, > >because when I remove it the exception changes to "no provider found for > >algorithm xxx". As I said I get the exception in my own program (an > Eclipse > >Plug-In) as well as when I run the sample that comes with the Apache API > (or > >CVS version). Signing works fine, encrypting keeps producing this > problem. > >Any other suggestions? I'm completely lost at this point. Thanks. > > > >Dominik -- "Sie haben neue Mails!" - Die GMX Toolbar informiert Sie beim Surfen! Jetzt aktivieren unter http://www.gmx.net/info
