rossoctl / rossoctl/cortex

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

Open
#946 0 comments 0 reactions 1 assignee View on GitHub

@huang195 is already working on this.

Since Sep 10, 2026.

enhancement high priority
Dominant language
Go
Stars
13
Forks
40
Avg merge
12h 17m
Merged PRs (30d)
156

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.