Skip to main content

Security for CODESYS Git

Warning

CODESYS Git will ignore the encryption settings for the CODESYS project (CODESYS Project Settings – Security). The project is not protected within the Git repository, whether local or remote.

We recommend the following security measures when using CODESYS Git:

  • Connect the remote server (where you share a project with others) whenever possible only via HTTPS with certificate encryption.

    Never accept a self-signed certificate via an https connection and never switch off the certificate check.

    Reason: CODESYS Git supports the three protocols file, http, and https for communication with remote servers. Communication is encrypted only via https. If you use http or file, then you need to provide the encryption in another way (for example, via VPN). The settings in Dialog: Options: Git apply to certificate handling. If the Accept self signed certificate option is not selected, then when the connection is established CODESYS Git first checks the certificate for the connection to the server from which the project should be cloned. If this certificate is not trusted, then you will be given the option of allowing the connection after a personal check. For more information, see also the instructions for creating a project via git clone on the following help page: Using git clone to create a new CODESYS project already in Git management

  • Use a PAT (Personal Access Token) for two-factor authentication for the connection to Git platforms such as GitHub or GitLab. This is now required by most platforms. You need to create the PAT and make it available in CODESYS Git. See the following help page for the settings regarding credentials: Dialog: Credentials needed

  • Use a .NET SecureString password when using the scripting interface. See the note on the following help page: Using the Git Scripting Interface

: