IJHack / QtPass

QtPass is a multi-platform GUI for pass, the standard unix password manager.
https://qtpass.org/
GNU General Public License v3.0
1.03k stars 162 forks source link

QTpass will not authenticate for git via ssh on Windows #590

Open AlpNov opened 2 years ago

AlpNov commented 2 years ago

Describe the bug When push/pull via the windows gui, remote is using ssh protocol, qtPass show:

Permission denied, please try again. 
Received disconnect from [server IP] port 10264:2: Too many authentication failures 
Disconnected from [server IP] port 10264 
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

This is similar error to what console git would return if entering passwords wrong too many time.

To Reproduce Steps to reproduce the behavior:

  1. Set up git and ssh on an ubuntu server
  2. Set up git repo for existing password
  3. Set up QtPass and QtPass folder on windows machine
  4. Clone repo
    git clone ssh://user@[server ip]:10264/path/to/repo
  5. Confirm QtPass see folder and password, decrypt passwords correctly
  6. Confirm git can push/pull via the command line:
    git push
    user@[server ip]'s password:
    Everything up-to-date
  7. Try to use push/pull arrow on QtPass
  8. Receive error:
    
    Permission denied, please try again. 
    Received disconnect from [server IP] port 10264:2: Too many authentication failures 
    Disconnected from [server IP] port 10264 
    fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.



**Desktop (please complete the following information):**
 - Windows 10
 - QtPass
 - git.exe

**Server (please complete the following information):**
 - Ubuntu 20.04
 - git
 - pass

**Additional context**
Private server, not github or bitbucket
1da1a172 commented 2 years ago

I hit the exact issue attempting to use an ssh key (protected with a passphrase). The FAQ suggested using git-gui--askpass as the git binary. For me, this just caused it to fail silently instead of fail with an error message.

I was using: