To use encryption due an update with our scripts there is an option called CERT inside. This variable can have three valid values (documented in the scripts too):
CERT=0 CERT=1 CERT=2
A value of 0 (zero) disables encryption, the other two enables it. As the CERT variable is the same, using the encryption is different between Windows and Linux. On a standard Linux distribution it works usually out of the box. So it is set to 1 on Linux per default, as it is disabled (0) on Windows per default.
Depending on the value there will be done some things in the scripts which are important for the functionality, but no additional configuration is needed. Exception is one option in the Windows script - I will come back to this later on.
Just for completeness: a value of 2 verifies the certificate of our website, a value of 1 doesn't. In both cases the connection is secure. We do not recommend to not use encryption beside of doing tests. The following steps have to be done to
As prerequisite there are two files needed (both are included in our Windows Client AddOn's)
- wget.exe, version 1.15 or greater
- ca-bundle.crt (certification authorities)
Copy both in your
C:\Windows  folder. Because - this is the exception mentioned above - there is another option CAFILE in the Windows script (only here) with the default value:
You can set the full path and filename here too, but as long you did the steps like recommended, it should not be necessary to change this option.
As a variation - the default setting from the script should work also, if you did install the Windows Client AddOn's using setup. In this case the file
ca-bundle.crt  is in the installed folder (like e.g.
C:\Program Files\DynDN.eS Client Tools ). Then the scripts for your dynamic hosts have to be saved and executed inside this folder.
Nevertheless in any cases, if you run into trouble: move/copy the certificate file in the Windows directory and set
Do not use spaces on the right side of the equal sign, except you know what you do!
Summarized: the file
ca-bundle.crt  have to be in the path or same folder as the executed update script. The last step is to set
save, run and test your script.
Hmm - what to say here? I don't have any idea. If you run into trouble on Linux refer to the documentation of your distribution.