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.

Sign up for GitHub

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

Jump to bottom

Update vendor crypto package (solves ssh agent issue) #158

Open
coopernurse opened this issue May 3, 2019 · 0 comments · Fixed by gecko655/sup#1
Open

Update vendor crypto package (solves ssh agent issue) #158

coopernurse opened this issue May 3, 2019 · 0 comments · Fixed by gecko655/sup#1

Comments

@coopernurse
Copy link

This week I was writing a Supfile and hit this error:

dialer failed ssh: handshake failed: ssh: disconnect, reason 2: Too many authentication failures
connecting to clients failed: connecting to remote host failed: Connect("[email protected]:22"): ssh: handshake failed: ssh: disconnect, reason 2: Too many authentication failures

I was able to fix this by adding this line to ssh.go:

config.HostKeyCallback = ssh.InsecureIgnoreHostKey()

But that's only available in more recent versions of the crypto package.

Is there any objection to updating the crypto deps?
coopernurse added a commit to coopernurse/sup that referenced this issue May 3, 2019
@coopernurse
Update vendor golang.org/x/crypto
da6d779 
Also modify ssh.go to include:

    config.HostKeyCallback = ssh.InsecureIgnoreHostKey()

We should review whether this is ok, or whether there's
a better callback function to use here.

Updating the vendor package solved my issue with ssh-agent
and allowed me to connect to a remote host even if I have
several keys registered with the agent.

Without this patch I have to clear my ssh-agent identity list
each time I use sup.

Fixes pressly#158
@coopernurse coopernurse mentioned this issue May 3, 2019
Closed
@gecko655 gecko655 mentioned this issue Jul 3, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@coopernurse