Sobelow.Config.TLSVerify (Sobelow v0.18.1)

View Source

Disabled TLS certificate verification

Reports literal verify: :verify_none in TLS options, including Gun's tls_opts map entries. It also catches hackney's :insecure and insecure: true options and the direct verify option in WebTransport connections. Disabling verification lets an attacker impersonate the remote server. Use :verify_peer and a trusted CA, including for self-signed services.

Configuration in dev.exs and test.exs is excluded with the rest of Sobelow's config checks. Source files are scanned regardless of the runtime environment; review guards around development-only calls. Dynamically constructed options are not resolved. Explicit Erlang SSL and Hackney imports are resolved within their scope.

Server-side :ssl calls and calls whose client/server role is unknown receive low confidence: disabling client-certificate authentication is normal for servers that do not require mutual TLS. Client connections with verification disabled receive high confidence.

Ignore this check with:

$ mix sobelow -i Config.TLSVerify

Summary

Functions

details()

id()

rule()

run(dir_path, configs, files)