Integrate with self-hosted GitLab about ssl4tor HOT 2 CLOSED

GITLAB SELF HOST REPO

Try the following options:

• 2: GITLAB_SERVER = 0.0.0.0, 127.0.0.1
• 1:keep GITLAB_PORT_1 on 80
• 1:keep GITLAB_PORT_2 on 443
• 1: keep GITLAB_PORT_3 on 23:22 (try 22:22? once https works, if ssh does not work).
• 2: put EXTERNAL_URL=https://0.0.0.0" (hardcoded), currently it is: EXTERNAL_URL=https://127.0.0.1"

gitlab.rb file

• 3: external_url 'https://localhost' or: 'https://0.0.0.0` or: external_url 'https://127.0.0.1`
• 1: nginx['ssl_certificate'] = "/etc/gitlab/ssl/localhost/public_key.crt"
• 1: nginx['ssl_certificate_key'] = "/etc/gitlab/ssl/localhost/private_key.key"
• 2: nginx['listen_port'] = 80 or nginx['listen_port'] = 443
• 1: nginx['listen_https'] = true

Convert certs or not?

Yes, but it should not matter.

• TODO: verify the content after the conversion is identical.

Strategy

• Modify the GitLab self host repo such that it takes the relevant parameters from a file named file_0.sh through the command line arg or through CLI.

• Modify the gitlab.rb content such that it takes the relevant content from a file named gitlab_0.rb through the command line arg or through CLI.

• Then create a script that loops through the configurations and deletes the qemu and re-creates a new qemu for each configuration.

• Then write a code that loops through all the desired settings, and creates all the commands.

• Then pass those arguments into the qemu to run on those configurations.

• Then create a script that verifies whether the https:localhost:80 gitlab is available or not.

• Then create some commands that gets the output of that script, (or ideally a screenshot of the browser at that state).

Then write a script that:

from ssl4tor.

Working settings were found for https://0.0.0.0:443 to access GitLab.

from ssl4tor.