I would like this to be the problem... Unfortunately (?) the message
digests DO match. Otherwise, the SignerInfo.verify(...) method would
throw an exception saying that message digests do not match. (try
modifying a byte in the message digest hardcoded, you'll catch it...)
the verify methods begins by comparing the message digests, before
checking the signature.
So, the problem is still here...
> My guess is that the message digests don't match. In other words, maybe
> Crypto.signText() is not signing the exact same bytes that you digested
> to create the messageDigest you hardcoded into your test program.
> Perhaps if you told us what you passed into Crypto.signText(). I can
> think of all sorts of possibilities, like mismatched character
> encodings, extra spaces somewhere, etc.
