Skip to content

feature: git, gh and ssh keep working with Cortex running #946

Closed

Description

@huang195

Feature Description

Cortex terminates TLS for traffic in its path. Anything else on the machine that speaks HTTPS
is collateral: if trusting ~/.cortex/ca/ca.crt breaks git push or gh pr create, nobody
leaves Cortex running — and these failures tend to be intermittent rather than obvious.

This issue covers the tools that use the OS trust store. Tools with their own trust store are
tracked separately.

Proposed Solution

  • git clone / fetch / push over HTTPS and over SSH
  • gh CLI: auth, PR and issue operations
  • ssh and scp
  • Callers that pin certificates or pass --cacert fail loudly with an actionable message,
    never intermittently
  • Document which tools need the CA and which are passed through untouched

Additional Context

Part of the Cortex v0.9.0 release. Gates exit criterion 2 (Cortex is invisible to everything
else). Related: #912 — a CA trust failure currently degrades into intermittent slowness
instead of a clear error.

Activity

  1. added this to the Release V0.9.0 milestone on Sep 10, 2026
  2. self-assigned this
    on Sep 10, 2026
  3. huang195 commented on Oct 11, 2026

    @huang195
    MemberAuthor

    Verified on main (e3c7b8e) on macOS with the laptop proxy running: git clone/fetch/push (dry-run) over HTTPS and ls-remote over SSH, ssh, and gh (auth, PRs, issues, api, run logs, release download) all work. github.com/api.github.com are passthrough-host; off-list hosts gh uses (actions results-receiver, Azure blob) are passed through as os-trust-only since #1358. A client pinning its own roots fails once, then is passed through as program-refused; not pursued further, as pinning is uncommon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

Relationships

None yet

Development

No branches or pull requests

Issue actions