This article is the third and final piece of a three-part series exploring cryptographic systems and encrypting data within a Microsoft SQL Server 2005 database.
It explores techniques for encrypting data in a Microsoft SQL Server 2005 database using asymmetric encryption.
This time the function outputs 0, indicating that the signature is no longer valid and, therefore, that the data has been changed.
Note that in a real world application we would more than likely encrypt the plaintext first (not store it directly), and then sign the encrypted ciphertext.
In particular, a sender can encrypt their message using their private key.