-
Notifications
You must be signed in to change notification settings - Fork 540
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
concurrent calls to git
cause issues with encrypted SSH keys
#411
Comments
I have a feeling this is due to concurrently calling Git. |
@mattfarina seems like we should be able to add a flag for I'll make a note of this in vsolver - I haven't implemented parallel fetch there yet, anyway, so the timing of this report is good. |
Also, not sure if this is related: Glide version ( When I run
|
|
As a workaround, can you add the offending key(s) to your SSH agent? |
That's quite a use case assumption. SSH agent is a security problem and not everyone wants to use it. |
Does dep handle this well? |
we don't right now, no. we do have a logical choke point we could exploit to enforce it relatively easily, but there hasn't been a direct complaint about it yet over there, so I've deferred it in favor of other things. |
@sdboyer have you thought about what a good solution would be? |
The only one i've been able to come up with doesn't necessarily qualify as "good" - probably more like "passable" 😄 We use the aforementioned choke point to throttle down all network activity to the point where all network calls are serialized. An environment variable (preferred) or flag (i'd rather not increase the surface area of the interface for this) then determines whether the throttling behavior is active. |
any update? |
Hello,
glide install
does not work for me, because the Git repositories it needs to pull from are accessible over SSH. I am authenticating against it with my SSH key. The key's private key is encrypted. The concurrent calls thatglide install
makes, cause issues with the passphrase dialogue on the shell. Only the password for the first password request can be entered. Further attempts just echo the entered on the shell. Hitting enter just causes each error message to appear.Please fix it. Decrypting my private key is not an option.
The text was updated successfully, but these errors were encountered: