On Jun 11, 2008, at 6:31 PM, Edward Z. Yang wrote:
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 do not like the current behaviour. I use plink for quite a while now
and did not have any problems with it. Now I see a lot of annoying
debug messages that distract me from git's messages.
We should find a better solution until 1.5.6, otherwise I'll revert
54b9e8917c44c before creating an installer.
Maybe we can avoid printing the debugging messages unless an error
occurs. Something like
git fetch ...
Error: '<Value of $GIT_SSH>' returned an error. Try "--ssh-debug"
for details.
git --ssh-debug fetch ...
<full debugging output here>
I am not sure if "--ssh-debug" is the best command line syntax. Maybe
we should adopt gcc's way of passing arguments to the linker and would
add an option "--ssh(,<FLAGS>)+", e.g. "-ssh,-v" would pass the "-v"
argument to the program configured in GIT_SSH. I don't know, however,
if this can be easily implemented with the existing parse-options.
Steffen
