From: matheus ribeiro <[EMAIL PROTECTED]>
Reply-To: MUSCLE  <[email protected]>
To: [email protected]
Subject: [Muscle] Re: Probs with muscle applet
Date: Sun, 6 Nov 2005 16:03:55 +0000

Then I tried the encrypt with RSA and no padding with success. After
> this the alggorithm is fixed to RSA with no padding and I get an 9c03
> error if I try tro used RSA with PKCS#1 padding. You should have the
> same behaviour. So if you want to sign something you must hash it, pad
> it on your own and encrypt the hash with RSA no padding.

yup.

This is muscletool's use of the musclecard API, not an applet issue (or an issue of the cardedge API). I always assume that muscletool's very limited sign capability had become tweaked at some point from its general solution: tweaked to emulate something (or participate in something) required perhaps by some Linux PAM scheme.

The bottom line is: dont accept muscletools do_sign() and do_encrypt(): rewrite them for your specific needs. They are good API demos, tho.


_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle

Reply via email to