Skip to main content

Git Configuration

Add and make changes to your Git client settings in this section. Only one configuration can be saved in DerScanner.

To successfully scan projects with submodules, helper = cache --timeout must be filled in. By default, Git does not cache credentials. Each connection will prompt for a username and password. In cache mode, credentials are stored in memory for a specified period of time, and removed afterwards. Please notice that the data is stored in your home directory in plain text.

Configuration example:

[user]
email = your@email.com
user = your_username
[credential]
helper = cache --timeout 30000

Ignoring the certificate​

To ignore Git validation of self-signed certificates, add a condition to the configuration text:

For all addresses:

[http] 
sslVerify = false

For a single address weak.example.com:

[http "https://weak.example.com"] 
sslVerify = false

Verifying the certificate​

If Git validation of self-signed certificates is required, then the following conditions must be met:

  1. Generate a self-signed certificate for the domain name (use the Common name option when creating).

  2. In the DerScanner interface (Admin Panel > System > Git Configuration), add to the Git configuration:

Add to trusted Git for all addresses:

[http]
sslCAInfo = /opt/backend/files/certs.crt

Add to trusted Git for a single address weak.example.com:

[http "https://weak.example.com"]
sslCAInfo = /opt/backend/files/certs.crt
  1. On the server with the APP module, create the /opt/derscanner/app/service/backend/files/cert.crt file and add the contents of the self-signed certificate in the following format:
-----BEGIN CERTIFICATE-----
CERTIFICATE_SAMPLE_1
-----END CERTIFICATE-----
  1. If necessary, new self-signed certificates can be added by editing the /opt/derscanner/app/services/backend/files/certs.crt file:
-----BEGIN CERTIFICATE-----
CERTIFICATE_SAMPLE_1
-----END CERTIFICATE-----
-----BEGIN CERTIFICATE-----
CERTIFICATE_SAMPLE_2
-----END CERTIFICATE-----
...