The padding block type 0 was deprecated after PKCS1 v1.5 and not even mentioned in the current version. The JC API also changed along the way to reflect this deprecation.
If you go back and look at the API document for JC2.1 you'll see that, unlike later versions, it doesn't mention the specific padding types supported. My guess is the javacard he's playing with is 2.1 compliant and not 2.1.1 or later compliant. I'm pretty sure that some of the egate's were 2.1. Mike At 07:50 AM 4/27/2009, Hendrik Tews wrote: > > According to PKCS1 - section 7.2 and 7.2.1 the recommendation > is to generate a new random padding string for each encryption > operation. The java implementation is following this > recommendation while the card probably isn't. > >I would say it depends on what cipher the card uses. If it is >ALG_RSA_PKCS1 (see javacardx.crypto.cipher) then it is probably >using the same padding scheme. If it is ALG_RSA_NOPAD, then it is >not using any padding. > >Bye, > >Hendrik >_______________________________________________ >Muscle mailing list >[email protected] >http://lists.drizzle.com/mailman/listinfo/muscle _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
