tls: failed to verify certificate: x509

[xu-xiang]

I used the --wait-for-insecure-skip-tls-verify parameter, but I still got a certificate error

./bin/ftw run -d regression/tests/ --config regression/cloud-test.yaml --debug  --include "^9994026" --wait-for-insecure-skip-tls-verify


🛠️ Starting tests!
🚀 Running go-ftw!
3:10PM DBG Applying overrides for engine '', platform ''
👉 executing tests in file 
        running 9994026-4026: Error: can't connect to destination &{DestAddr:10.0.0.5 Port:443 Protocol:https}: tls: failed to verify certificate: x509: certificate signed by unknown authority 

cloud-test.yaml

mode: 'cloud'
testoverride:
  input:
    dest_addr: "10.0.0.5"
    port: 443
    protocol: https
    headers:
      Host: "test.waf.com"
  output:
    expect_error: true

[theseion]

Thanks for reporting @xu-xiang. It looks to me like it's a setup issue in our code, since wait4x requires a host address as its first argument. Could you try the same but also supply the --wait-for-host flag?

[tgragnato]

Hi @theseion, thanks for looking into this!
I don't think this is a setup issue related to the wait4x package.

From the test output, it is clear that the check by the wait4x package was successful; after this, the test run started, only to fail immediately.

The problem is that currently, there is no flag that allows you to bypass TLS validation during the execution of the tests.

You can verify this by adding the option InsecureSkipVerify: true to the tls.Config struct in the ftwhttp/client.go file. At this point, the runs will proceed successfully even when the certificate setup is incorrect.

[theseion]

Thanks for the analysis @tgragnato. I'll check.

[theseion]

You're right. There's currently no option to configure this. I'll add it.