6.4.4 Local Machine ECDSA Signing
6.4.4 Local Machine ECDSA Signing
How Signing works on Local Machine
SecureSIGNING takes place only on the LOCAL Machine.
On a Local Machine, the Private and the Public Keys co-exist. SecureSIGN makes use of the Private Key to sign SecureUPDATE files and the Public Key to validate them.
Steps to accomplish SecureSIGN:
Step 1: The binary data difference file is created in the form or a SecureUPDATE file (SecureDELTA or XtremeDELTA)
Step 2: The Private/Public Key pair is generated using the ECDSA algorithm.
Step 3: SecureUPDATE files are encrypted using Public Key data.
Step 4: Depending on the chosen method, an MD5 or a SHA256 is computed on the whole SecureUPDATE diff file from Step 1.
Step 5: The MD5 or the SHA256 generated is signed using the Private key and the ECDSA algorithm.
Step 6: SecureUPDATE header file information is encrypted and secured.
