Secure ENCODING vs Secure DECODING:


SecureENCODING vs SecureDECODING.


Here is a short table to understand what files are used, how and where.


TRANSFORM

FILE 1

FILE 2

OUTPUT

LOCATION

CONTEXT

SecureENCODING

Source (initial, old) file

Target (new) file

SecureDELTA file

TEST PC

(LOCAL)

Encoding Step (Encode Page) within SecureDELTA Application

not needed

SecurePATCH file

Installer Step (Installer Page) within SecureDELTA Application

SecureDECODING

Source file (*)

SecureDELTA file

Target file (**)

TEST PC

(LOCAL)

For testing purposes only.

Decoding Step (Decode Page) within SecureDELTA Application

SecurePATCH file

USER PC

(REMOTE)

SecurePatching of Source file!

Comments:

Source file is ALWAYS required in Encoding and Decoding and its content MUST not CHANGE!







Please NOTE:


(*) - Do not attempt to update a file that can change or has been changed already, on user's machine, before you apply the SecurePATCH file. 

The source file from the User machine has to be bit-by-bit identical, otherwise the SecureUPDATE process will not start.


(**) - this file is a replica bit-by-bit of the Target file from the TEST PC, that has been used to create the SecureDELTA binary diff.

The source (old) and the target files usually have the same name, therefore, the source file will get renamed on user's machine.