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.
A username is required to authenticate with an SSH server. A public key alone is not enough.
While true, in most cases the username is simply “git” and not a specific username tied to the pub/priv keypair
The post you originally replied to was misunderstanding how the username is located when authenticating with a server.
Original post:
Your reply would be creating more confusion, because you implied that no username is required.
Your reply:
I am just clarifying if the original poster read your comment and was led to believe they wouldn’t need a username. It is, in fact, required. As you expressed, it’s usually “git” when connecting to a a git server, but it doesn’t have to be.