Skip to content
This repository has been archived by the owner on Jul 1, 2020. It is now read-only.

Signing & Verifying Patches

Süleyman Yasir KULA edited this page Mar 7, 2020 · 11 revisions

As an additional layer of security against man-in-the-middle attacks, you can sign your VersionInfo and/or PatchInfo files. Then, while patching your app, you can verify their signatures to make sure that they are genuine. This will ensure that the hashes and filesizes stored in these files are not tampered with; which, in turn, makes it possible to detect whether or not downloaded patch files are genuine.

Signing & verifying your patches is optional but is highly recommended.

Built-in Method

To use the built-in functions to sign/verify your patches, you must first generate an RSA key pair. Then, you can sign & verify your patches with these keys:

Custom Method

It is also possible to write your own functions to sign/encrypt and verify/decrypt your patches instead of using the built-in functions.

SimplePatchTool doesn't need to know how you sign or encrypt these files, so feel free to use any code/application for this job. You just have to let SimplePatchTool know how to verify/decrypt your patches, which can be achieved via the UseVersionInfoVerifier and/or UsePatchInfoVerifier functions of SimplePatchTool.

Clone this wiki locally