Using SSH keys with GitLab CI/CD | GitLab
docs.gitlab.com
GitLab product documentation.

I was reading GitLab’s documentation (see link) on how to write to a repository from within the CI pipeline and noticed something: The described Docker executor is able to authenticate e.g. against the Git repository with only a private SSH key, being told absolutely nothing about the user’s name it is associated with.
If I’m correct, that would mean that technically, I could authenticate to an SSH server without supplying my name if I use a private key?

I know that when I don’t supply a user explicitly like ssh user@server or via .ssh/config, the active environment’s user is used automatically, that’s not what I’m asking.

The public key contains a user name/email address string, I’m aware, is the same information also encoded into the private key as well? If yes, I don’t see the need to hand that info to an SSH call. If no, how does the SSH server know which public key it’s supposed to use to challenge my private key ownership? It would have to iterate over all saved keys, which sounds rather inefficient to me and potentially unsafe (timing attacks etc.).

I hope I’m somewhat clear, for some reason I find it really hard to phrase this question.

  • xantoxis@lemmy.world
    5·
    6 months ago

    EDIT: Noticed you’re talking about Gitlab in the question, and I responded about Github, but I’m certain that gitlab does everything the same way, because that’s all the technology is capable of. (I have no way to test the ssh -T command at the end for gitlab, though, so ymmv.)

    To clear up some minor confusion here:

    1. Github knows nothing about your private key. There’s very little metadata stored in the private key, and github.com has access to none of it. That includes email address or identity.
    2. Github has identity information stored for you, and then, separately, you uploaded a public key. The public key also contains no information about you, but github knows it’s part of your account. Additionally, github enforces a requirement that your public key can’t be uploaded to any other account, for the reason I’m about to state below.
    3. Github has an index built of everyone’s public keys (or more likely their digests, although the technical details of the index are not something known to me–and it doesn’t matter). When it sees an authentication request, it looks up the digest in the index, which maps to a user account.

    At this point it already knows who is trying to authenticate. Once your authentication request succeeds with your public key (the usual challenge-response handshake associated with asymmetric cryptography), github interacts with your ssh client (most likely git) applying the permissions of your user and your user account.

    BTW, github has a documented method for testing the handshake without doing any git operations:

    ssh -T [email protected]

    Depending on your ssh config, you might also need to supply -i some_filename.pem to this. Github will reply with

    Hi aarkon! You've successfully authenticated, but GitHub does not provide shell access.

    and then close the connection.

    Note that the test authentication uses the username git and, again, contains no information about who you are. It’s all just looked up on github’s side.