proomt

Search

Search posts, papers, and topics

All posts

Mozilla Automation TeamJonathan Almeida1 min readtutorialintro

SSH access to Github over HTTPS

Summary

GitHub also accepts SSH connections on port 443 (HTTPS). Add a host entry in your SSH config pointing github.com to ssh.github.com on port 443 to bypass restrictive firewalls.

  • GitHub runs an SSH service on ssh.github.com:443 for environments where port 22 is blocked.
  • Configure SSH client once; all future git operations over SSH will use the alternate port automatically.

Allows developers to use SSH‑based Git workflows (e.g., signed commits, key‑based auth) from networks that block outbound port 22, without switching to HTTPS URLs.

3/10

Related reading

  1. Inside ZCode: Silently uploading your Git history to the cloud

    ZCode (Zhipu’s AI coding desktop) silently archives your entire workspace—including full .git history, LFS cache, and config—encrypts it with a server‑supplied RSA public key, and uploads the ciphertext directly to Aliyun OSS. The upload runs unconditionally for any logged‑in user, cannot be disabled via UI, and the decryption key lives only on the server, giving Zhipu full read access to your co…

    Hacker News front pageferstar.org6 minpostmortemHN336113
  2. Replica-aware routing public beta

    Replica‑aware routing (public beta) lets ClickHouse Cloud users pin a query stream to a specific replica by sending a custom header (HTTP) or overriding the TLS SNI (native). The proxy (Envoy) hashes the tag and consistently forwards all requests with the same tag to that replica, giving read‑after‑write consistency for temporary tables, session objects, and warm replica caches. Stickiness is bes…

    ClickHouseclickhouse.com6 min