# [bug] git 2.6.2 (64-bit) blocks keyboard input (running in RDP, Win7 x64) 3 messages from 2015-11-10 to 2015-11-16. Participants: Ryabov, Vasily V, Johannes Schindelin. Thread: https://gitlist.dev/t/40762 ## Ryabov, Vasily V, 2015-11-10 14:02 Subject: [bug] git 2.6.2 (64-bit) blocks keyboard input (running in RDP, Win7 x64) Message-ID: URL: https://gitlist.dev/e/D28D2D5A78DB8B49BB75DB10E72239683ABA1700%40IRSMSX102.ger.corp.intel.com ``` Hi, I'm trying to run something like this (on the remote machine (Win7 x64 with git 2.6.2 64-bit) through RDP): ˋˋˋ git pull --tags --progress ssh://@:/ +refs/heads/*:refs/remotes/origin/* ˋˋˋ It worked on local machine with git 1.9.5. Git asks to confirm an action: ˋˋˋ The server's host key is not cached in the registry. You have no guarantee that the server is the computer you think it is. The server's dss key fingerprint is: ssh-dss 1024 <...> If you trust this host, enter "y" to add the key to PuTTY's cache and carry on connecting. If you want to carry on connecting just once, without adding the key to the cache, enter "n". If you do not trust this host, press Return to abandon the connection. Store key in cache? (y/n) ˋˋˋ I'm typing `y`, but there is no reaction at all. No symbols appears in the console. But... When I'm pressing `Ctrl+C`, it's killed. And I can see `yyyyy` keys in the bash console for the next command. On-screen keyboard didn't help as well. I've already tried several combinations of `MinTTY` and `Windows cmd.exe` check boxes in the installer. Nothing helped. It looks like a bug in Git client. Best regards, -Vasily. -------------------------------------------------------------------- Joint Stock Company Intel A/O Registered legal address: Krylatsky Hills Business Park, 17 Krylatskaya Str., Bldg 4, Moscow 121614, Russian Federation This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ``` ## Johannes Schindelin, 2015-11-16 12:10 Subject: Re: [bug] git 2.6.2 (64-bit) blocks keyboard input (running in RDP, Win7 x64) Message-ID: URL: https://gitlist.dev/e/alpine.DEB.1.00.1511161308510.1686%40s15462909.onlinehome-server.info In-Reply-To: ``` Hi Vasily, On Tue, 10 Nov 2015, Ryabov, Vasily V wrote: > I'm trying to run something like this (on the remote machine (Win7 x64 with git 2.6.2 64-bit) through RDP): > ˋˋˋ > git pull --tags --progress ssh://@:/ +refs/heads/*:refs/remotes/origin/* > ˋˋˋ > It worked on local machine with git 1.9.5. > > Git asks to confirm an action: > ˋˋˋ > The server's host key is not cached in the registry. You > have no guarantee that the server is the computer you > think it is. > The server's dss key fingerprint is: > ssh-dss 1024 <...> > If you trust this host, enter "y" to add the key to > PuTTY's cache and carry on connecting. > If you want to carry on connecting just once, without > adding the key to the cache, enter "n". > If you do not trust this host, press Return to abandon the > connection. > Store key in cache? (y/n) > ˋˋˋ > I'm typing `y`, but there is no reaction at all. No symbols appears in the console. But... > When I'm pressing `Ctrl+C`, it's killed. And I can see `yyyyy` keys in the bash console for the next command. This is a known issue, mentioned in the release notes (https://github.com/git-for-windows/build-extra/blob/master/installer/ReleaseNotes.md#known-issues): > * If configured to use Plink, you will have to connect with putty first > and accept the host key. Ciao, Johannes ``` ## Ryabov, Vasily V, 2015-11-16 12:21 Subject: RE: [bug] git 2.6.2 (64-bit) blocks keyboard input (running in RDP, Win7 x64) Message-ID: URL: https://gitlist.dev/e/D28D2D5A78DB8B49BB75DB10E72239683ABA2037%40IRSMSX102.ger.corp.intel.com In-Reply-To: ``` Hi Johannes, Thanks for your response. I've already workarounded the issue by using OpenSSH. It seems there is no simple way to configure Jenkins Git plugin to call Putty first under LOCAL_SYSTEM account, so using OpenSSH is much simpler in this case. Best regards, -Vasily. -----Original Message----- From: Johannes Schindelin [mailto:Johannes.Schindelin@gmx.de] Sent: Monday, November 16, 2015 3:10 PM To: Ryabov, Vasily V Cc: git@vger.kernel.org Subject: Re: [bug] git 2.6.2 (64-bit) blocks keyboard input (running in RDP, Win7 x64) Hi Vasily, On Tue, 10 Nov 2015, Ryabov, Vasily V wrote: > I'm trying to run something like this (on the remote machine (Win7 x64 with git 2.6.2 64-bit) through RDP): > ˋˋˋ > git pull --tags --progress > ssh://@:/ > +refs/heads/*:refs/remotes/origin/* > ˋˋˋ > It worked on local machine with git 1.9.5. > > Git asks to confirm an action: > ˋˋˋ > The server's host key is not cached in the registry. You have no > guarantee that the server is the computer you think it is. > The server's dss key fingerprint is: > ssh-dss 1024 <...> > If you trust this host, enter "y" to add the key to PuTTY's cache and > carry on connecting. > If you want to carry on connecting just once, without adding the key > to the cache, enter "n". > If you do not trust this host, press Return to abandon the connection. > Store key in cache? (y/n) > ˋˋˋ > I'm typing `y`, but there is no reaction at all. No symbols appears in the console. But... > When I'm pressing `Ctrl+C`, it's killed. And I can see `yyyyy` keys in the bash console for the next command. This is a known issue, mentioned in the release notes (https://github.com/git-for-windows/build-extra/blob/master/installer/ReleaseNotes.md#known-issues): > * If configured to use Plink, you will have to connect with putty first > and accept the host key. Ciao, Johannes -------------------------------------------------------------------- Joint Stock Company Intel A/O Registered legal address: Krylatsky Hills Business Park, 17 Krylatskaya Str., Bldg 4, Moscow 121614, Russian Federation This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. ```