LizardNet Code Review/PuTTY-Gerrit bug

From LizardWiki, FastLizard4's wiki and website
Jump to: navigation, search

A bug has been discovered in the version of Apache SSHd that LizardNet Code Review uses. This bug seems to only affect Git users who use PuTTY instead of OpenSSH as their SSH provider; likewise, this bug usually only appears on Windows systems. Until Apache SSH is patched, a minor workaround exists for the bug that will allow users to effectively bypass it.

The bug usually occurs when cloning a Git repository from LizardNet Code Review by SSH, though it may also occur on pulls or fetches. Git will pull changes just fine, but will hang at Resolving deltas: 100% (n/n), done.. If you are on Windows and/or are using PuTTY as your Git SSH provider, please follow these directions to work around the issues:

Resolution

  1. Launch PuTTY. If you can't find it on your computer, you can simply redownload it from here, as all PuTTY instances on a single computer use the same registry entries for configuration.
    • If you use GitExtensions, make sure you have PuTTY set as your default SSH client. Go to Tools > Settings and click SSH in the section list on the left. Make sure PuTTY is selected under Specify which SSH client to use.
  2. In the PuTTY Configuration window, in the section list on the left, go to Connection > SSH > Bugs.
  3. Under Detection of known bugs in SSH servers, find Chokes on PuTTY's SSH-2 'winadj' requests. Set this to On
  4. In the section list on the left, go back to Session at the very top
  5. Under Load, save or delete a stored session, click Default Settings, then click the Save button.
  6. Close PuTTY. You should now be able to clone a LizardNet Code Review Git repository successfully.

See Also

For more information, please see the following links:

Retrieved from "https://fastlizard4.org/w/index.php?title=LizardNet_Code_Review/PuTTY-Gerrit_bug&oldid=2692"