The "signature" in the case of a decryption/encryption event is just the decrypted/encrypted text.
cool, but why call it signature then? is there a restriction of what fields can be passed back and forth from the signer and the app?
Probably old name when the app only did signatures.
I had to do some digging in the source to figure out why it was seg faulting at one point and it does appear that way