> The problem with IN objects is, that there is always an additional write > cycle. If everything is contained in an APDU, this cycle does not occur. > Another thing is, that enough space in the Mem/ObjectManager must be > free for this. Further if you sign bigger documents, then the space on a > smartcard is never enough, multiple CIPHER_PROCESS instructions are > necessary.
I modified my version of ComputeCrypt so it could verify an existing (long term storage) object, previously stored in the object manager, of any size. It parses the object, assuming it to be a cert TLV, identify the toBeSigned block, and the signature block, and otherwise use a variation of the process I mentioned. The consuming applet of these methods just created 3 simple stimuli: init, process, finalize, where the DL_XXX value identified the object to be verified. I had to extend the protocol slightly, to introduce some signaling of the feature requests (more DL_XXX values). I can share this if you want, and perhaps you generalize it into the rest of the re-thinking and redesign work you are doing. _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
