Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 382
    • Issues 382
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #568
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

push using ssh private key with a password fails the first time

By berko... on September 28, 2010 09:35 (imported from Google Code)


What steps will reproduce the problem?

  1. Clone a repository over ssh using a private key (made with putty) that is password-protected
  2. Make some changes, commit, then push.

What is the expected output? What do you see instead?
Expected: A message box pops up asking for the private key password, then after successfully unlocking the key the push is attempted.

Actual: A message box pops up for the private key password, but at the same time the push is attempted, and in the background a window pops up that asks for the ssh password (because the key was not yet unlocked). At this point you can't do anything if you don't know the password and you have to let the ssh authentication fail and start over.

After doing this, if you unlocked the key from the first window, then putty (if you're using putty) keeps the key unlocked so this procedure works correctly the second time without asking for a password to unlock the key.

On a side note, if you a very fast and type the password before the second window pops up, then it succeeds from the first time :) (because the key is unlocked before attempting to ssh authenticate)

What version of the product are you using? On what operating system?
1.5.3 on WinXP SP3

Please provide any additional information below.
This is pretty minor and the fix is hopefully easy, but I'm not sure how you'd be able to check if the key is unlocked... In any case, fantastic work and thanks for making our lives easier every day!

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking