mirror of
https://github.com/QuasarApp/qca.git
synced 2025-05-07 08:19:33 +00:00
in the docs, explain that signatures are more than just hash+pubkey operations
svn path=/trunk/kdesupport/qca/; revision=1062589
This commit is contained in:
parent
014595173f
commit
177149f8b4
@ -59,6 +59,14 @@ enum EncryptionAlgorithm
|
||||
|
||||
/**
|
||||
Signature algorithm variants
|
||||
|
||||
Note that most signature algorithms follow a process of first hashing the
|
||||
plaintext data to be signed, creating a payload format that wraps the hash
|
||||
value (among other things), and then signing the payload with the private
|
||||
key. So, for example, an EMSA3(SHA1) signature outputted by QCA cannot be
|
||||
verified by merely performing RSA and SHA1 operations (e.g.
|
||||
"openssl rsautl -verify" and comparing with sha1sum), because that would not
|
||||
take the EMSA3 payload format into consideration.
|
||||
*/
|
||||
enum SignatureAlgorithm
|
||||
{
|
||||
|
Loading…
x
Reference in New Issue
Block a user