6.4.7 Signing SecureUPDATE file(s) - Part II


  Signing SecureUPDATE file(s) - Part II


Once the HASHING algorithm is selected, SecureDELTA App carries out the steps 3 to 6 (see full picture here):


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.

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.


There is also a NOTE that accompanies the signing action:




A progress bar also displays, especially useful when signing large files. It estimates the entire process and displays remaining time, as well.




The signing process finalizes with the update of the text information area on "...file is already signed"


ECDSA Signing Process is now completed!


You have now the possibility to verify (validate) the SecureUPDATE file by using the Public Key file.