Skip to content
Gitdown Developer Docs

Git over SSH

Git SSH is served at dev.gitdown.io on port 22 through the same reserved anycast IP as HTTPS, but outside the HTTP URL map.

git@dev.gitdown.io:<OWNER>/<REPOSITORY>.git

Use the clone URL shown by the Gitdown UI for the canonical user- or organization-owned path. An enrolled key resolves to exactly one human or one active grant-bound bot credential before repository authorization runs.

Key policy

Section titled “Key policy”
  • Prefer ssh-ed25519.
  • RSA is accepted only at 3072 bits or stronger.
  • DSA, ECDSA, undersized RSA, PuTTY, SECSH, and PEM-only public-key formats are rejected.
  • Enroll a single-line OpenSSH public key. Never upload or paste private key material.
Terminal window
ssh-keygen -t ed25519 -f <PROTECTED_KEY_PATH>
ssh -p 22 -T git@dev.gitdown.io

SSH permits only git-upload-pack and git-receive-pack. It rejects shells, PTYs, SFTP, environment injection, X11, and port forwarding. Repository access and all append-only main, signed-push, branch, CI, and rate/size policies remain identical to HTTPS.

Bot SSH keys are separate credentials bound to one grant. Revocation or live authority loss invalidates their use without relying on commit metadata or an old session cache.