> Clifford Caoile wrote: > > As an aside, I tried this with "github"'s ssh upload service. I > > initially had trouble with the host key authentication when I did a > > git.cmd push ... The problem was that I didn't have the host key > > cached in the registry, because this was my first time to use > > "github". Also plink called in this way does not > interactively query > > the user if the host key is not cached. So I typed "%GIT_SSH% > > github.com" at the cmd prompt and then accepted the host key as > > presented (hoping that MITM attackers were away, how can > you verify it > > separately?), which added it to the cache. After that git.cmd push > > worked. Call me out as a plink.exe novice, if you must. > > This is exactly the problem I was complaining about when I > wrote my plink/custom port patch. Plink *does* attempt to be > interactive. > However, there's a problem between stdin communication between git > (MingW?) and plink (native Windows apps?). No one I've talked > to has a solution for this problem, unfortunately.
I somehow thought the whole point of including PuTTY / plink support is to enable users that already use PuTTY to specify a PuTTY session name instead of a host name to connect to. And if there already is a PuTTY session, the user very likely already connected to that server and accepted the host key. This is the only way I use plink, I never call plink with a hostname. Using plink with PuTTY sessions also has the advantage that you do not need to have pageant running in the background, as you can directly specify in the session's settings which private key to use. -- Sebastian
