Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

vcstool cannot be used with ssh repositories with passphrase for the identity file #212

Closed
galou opened this issue May 14, 2021 · 5 comments

Comments

@galou
Copy link

galou commented May 14, 2021

Either there is a problem with my configuration or vcstool cannot be used with ssh repositories with passphrase for the identity file. I have such a repository and when I used vcs import < my.repos, I see the prompt Enter passphrase for key '....':, I then type my passphrase but see EEE and then I'm asked for a password, as then happens when the passphrase is incorrect.

vcs import --input my.repos doesn't help.

@galou
Copy link
Author

galou commented May 14, 2021

Maybe related to #128 ?

@christophebedard
Copy link
Contributor

Not sure about #128, but look at #23 and #124. There is a solution/workaround documented here: https://github.com/dirk-thomas/vcstool/blob/master/README.rst#parallelization-and-stdin. Just use --workers 1 so that you can enter a password.

@galou
Copy link
Author

galou commented May 17, 2021

The README files states In the case repositories are using SSH git@ URLs but the host is not known yet vcs import automatically falls back to a single worker but this was not the case for me (v 0.2.15).

@galou galou closed this as completed May 17, 2021
@christophebedard
Copy link
Contributor

christophebedard commented May 17, 2021

I see! That feature seems to be in >=0.2.5 so if it wasn't working for you then it might be a bug.

Looks like it's simply running ssh-keygen -F $HOST (e.g., ssh-keygen -F github.com) for all hosts and if one of the return codes is non-zero (unknown host) then it uses 1 worker. Maybe all the hosts are known on your machine?

*oops I misread and interpreted that as "it was not working for me"

@galou
Copy link
Author

galou commented May 18, 2021

All the hosts should be known but their access requires giving a passphrase, which doesn't work with multiple workers. I cannot test the workaround but I guess it works, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants