On Jun 12, 2008, at 12:39 PM, Schuberth, Sebastian wrote:
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.
We could probably write another cmd wrapper script (that GIT_SSH
points
to) that contains something like
echo y | plink %*
hoping that the "y" will no no harm if the server key already is in
the
cache.
Asking the user for explicit confirmation of a hostkey is an integral
part of SSH's security concept, so I'm against automatically accepting
host keys. The confirmation message prints the fingerprint of the host
key, which could in principle be verified.
Steffen
