SSH, Actually 100% signal, 0% noise.

Git over SSH

concept
depth 2/3 − deeper + surface

With GitHub, GitLab, and similar services, SSH is used as authentication, not login. You never get a shell—you only prove identity, the service decides what you can access based on that identity, and each git operation is a separate authentication.

Two models, one protocol.

The traditional model (server login): you get a shell, you run commands, you browse the filesystem, the connection stays open.

The git hosting model (authentication only): no shell, ever. You prove identity; the service does the rest.

When you run:

git clone [email protected]:user/repo.git

behind the scenes:

  1. Git opens an SSH connection to github.com
  2. You prove identity using your SSH key
  3. GitHub checks: "Does this key have access to this repo?"
  4. If yes → sends repository data
  5. Connection closes

No shell. No commands. Just cryptographic proof of identity.