Hi there, The transport protocol of the SSH package supports key changes, but has a mandatory key change at the start. Handling this has been a source of hard to reproduce bugs, eg.
https://go.googlesource.com/crypto/+/d68c3ecb62c850b645dc072a8d78006286bf81ca https://go.googlesource.com/crypto/+/6fb066875c8002ccd49dbd9a16b522711cb8f59d https://go.googlesource.com/crypto/+/77014cf7f9bde4925afeed52b7bf676d5f5b4285 https://github.com/golang/go/issues/19639 one of the complicating factors is that I can't think of a good way to test for this behavior. Ideally, I would want to run a set of handshakes where goroutine speeds are perturbed so all different orderings of events are covered. Has anyone ever created something that would do this? -- Google Germany GmbH, Erika-Mann-Strasse 33, 80363 Munich Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Matthew Scott Sucherman, Paul Terence Manicle -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
