Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
x/crypto/ssh: msgNewKeys interpreted too soon #18850
"We've also run into a different issue during the kex/handshake.
panic: ssh: no key material for msgNewKeys
We were previously running golang/crypto@ca7e7f1"
changed the title from
msgNewKeys interpreted too soon.
x/crypto/ssh: msgNewKeys interpreted too soon
Jan 30, 2017
I took a look at this , but it's puzzling.
Can you confirm that your code runs cleanly under the race detector?
We run all our tests with the race detector and haven't had any complaints from that lately.
What would happen if a client sends a kex with FirstKexFollows set? I can try to test that (using dropbear), but it's just a guess at this point.