1. TortoiseHg
  2. TortoiseHg
  3. thg
Issue #1760 resolved

Can't use repositories over SHH with Pageant and TortoiseHg 2.3.x (No supported authentication methods available)

Francesco Lodolo
created an issue

I use Pageant to load my SSH key on Win 7 Pro 64bit and TortoiseHg to manage my repositories (Mozilla l10n). While TortoiseHg up to version 2.2.2 works fine, with versions 2.3.x I can't use these repositories anymore.

For example I try to clone this repository. Source: ssh://name@example.com@hg.mozilla.org/l10n-central/it/ Hg command: hg clone --verbose -- ssh://name@example.com@hg.mozilla.org/l10n-central/it/ d:\test

After a few seconds I get an alert with title "PuTTY Fatal Error" and message "Disconnected: No supported authentication methods available (server sent: publickey,gssapi-with-mic).

Log: % hg clone --verbose -- ssh://name@example.com@hg.mozilla.org/l10n-central/it/ running "TortoisePlink.exe" -ssh -2 name@example.com@hg.mozilla.org "hg -R l10n-central/it/ serve --stdio" no suitable response from remote hg [command returned code 255 Wed Mar 14 12:44:51 2012]

If I reinstall TortoiseHg 2.2.2 everything returns to normal.

Comments (6)

  1. David Wilhelm

    I'm unable to reproduce when cloning over ssh from bitbucket (on Win 7 Home x64). Do you get the same error from both the command line and through thg, or only when cloning through thg?

  2. Francesco Lodolo reporter

    Same behavior running from the command line. The error comes up after this command

    TortoisePlink.exe -ssh name@example.com@hg.mozilla.org -2 "hg -R l10n-central/it/ serve --stdio"

    To be more specific, I can't do anything with the repository (even pull over ssh on an existing repository cloned with 2.2.2)

  3. Francesco Lodolo reporter

    You're absolutely right. Version shipped with TortoiseHg is 0.60.0.0, I downloaded version 0.62.0.0 and everything went back to normal.

    Not sure what I should do with this issue at this point (edit the title, close it as resolved?).

  4. Anonymous

    Francesco, I'd just leave it how it is. The current title and description are what will probably lead others to it if they have the same problem. And it is technically a bug. The additional information will just help the contributors to fix it more quickly.

    If you're feeling really ambitious, you could fix the code yourself, since it's an open-source project. :-)

  5. Log in to comment