cryptomgmtlibs/securitydocs/doxygen_docs/Security_intro_signatures.dox
author Santosh V Patil <santosh.v.patil@nokia.com>
Fri, 13 Nov 2009 15:59:20 +0530
branchRCL_1
changeset 22 1440dc310db1
parent 0 2c201484c85f
child 8 35751d3474b7
permissions -rw-r--r--
Fix for bug 805. Added bld.inf to rootcertificates component for exporting the SWI certificate store.

/**
@page Security_signatures Digital signatures

A digital signature is used to verify that a message (or data) actually came from the sender (the one who signed the 
message) and that it has not been tampered with.

A signature is formed by producing a fixed-length digest (@ref hash) of the message using a hash algorithm, which is then 
encrypted using the sender's private key. This signature and the message are then sent to the recipient.

The receiver can then verify the signature as follows: a @ref hash is produced of the sender's message (using the hashing 
algorithm sent with the signature); also, using the sender's public key, their signature is decrypted into a @ref hash. 
These two hashes are compared: if they are the same, it is more or less certain that the public key used for the 
@ref decryption corresponds to the private key used to create the signature, thus data integrity is validated.


*/