Is there a (hopefully simple) way to tie an SSH keypair to an arbitrary (remote) repo instance?
If I am doing bk operations on a repo on machine A that needs to push/pull/diff whatever with a related repo on machine B, I’d like to be able to specify an ssh keypair that would be used for these bk-specific communications.
Thanks, Wayne - I knew about that one and we might be able to make it work. My concern about this method is that we’d have to change the variable each time we wanted to switch to a different host. If we could find a way to have bk select the keyfile based on the target host, that might be a lot easier. I’ll say that I don’t know what the right answer is here…
The identityfile for bk needs to be different from the one used by the user in this case.
It may be that we need to do a much deeper study of the way we’re going to use this to see if we can “make it go” with the ~/.ssh/config file. But what you describe might still be the best way to go.
and when bk evaluates BK_RSH, assuming my-bk-config is sourced in a way that it is exec’t by the shell, then my-bk-config will need to be able to determine the target host (we can probably tell if it’s the local host, if it’s a parent, or if a different host was given on the command line) and choose the correct key that way.