Repository navigation
use behind a corporate proxy or with tls inspection is neither documented nor tested #25
Description
Measured
Cargo.toml:19: reqwest is compiled withsystem-proxy.Cargo.lockincludesrustls-platform-verifier, which uses the system certificate store.- The README does not mention
HTTPS_PROXY/NO_PROXYor corporate CAs, and there is no test for this case.
Why it matters
Beta testers in enterprises and MSSPs that reach the Internet through a proxy: it is common in their networks and they do not know whether the CLI will work.
Acceptance criteria
- The README has a networking section with the proxy variables that are honoured, the use of the system certificate store for corporate CAs, and how to diagnose with
--verbose. - It has been tested behind a TLS-inspecting proxy on Linux, macOS and Windows.
Depends on
Nothing.
Activity
[-]el uso tras un proxy corporativo o con inspección tls no está documentado ni probado[/-][+]use behind a corporate proxy or with tls inspection is neither documented nor tested[/+]Fix the proxy test's expected error prefix and record Linux verification
d0ubl3g commentedon Oct 12, 2026
Progress, shipped in 0.4.0 (https://github.com/Hodeitek/hodeishield-cli/releases/tag/v0.4.0), by #89 and #96:
--verbose.proxy-tlsworkflow).Still open: the same test on macOS and Windows. This issue stays open until both are measured.
d0ubl3g commentedon Oct 16, 2026
The proxy and TLS inspection test (
.github/workflows/proxy-tls.yml) now runs onubuntu-latest,macos-latestandwindows-latest(#194). All six cases pass on each, including TLS inspection with a custom CA installed in the system store (System keychain on macOS,LocalMachine\Rooton Windows), andSSL_CERT_FILEhaving no effect on macOS and Windows, as the README says. Still open: the same check on a real macOS and Windows 11 machine behind a proxy.