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.
The darker the roast, the lighter a bean should be. You could count a number of beans you have your numbers right and get decent results with, weigh them, and thus compare their roast to that of other beans. That way you‘d be able to find out if your achieved ratios are tied to the roast. Maybe you could even work out a scale telling you what to expect, a ballpark to get your ratio somewhat right when opening a new bag of beans.
That said, I’m only citing theory here, don’t take what I say as the last word on anything :)