https://bugzilla.mindrot.org/show_bug.cgi?id=845
--- Comment #21 from Darren Tucker <[email protected]> --- Another thing found to cause this in at least one case: ssh's hardware-accelerated GCM ([email protected]) running on the same CPU (a Xeon E5-2620 v4) as a hardware-accelerated sha1sum process. Switching the ssh session to [email protected] worked around the problem (presumably since it avoids HW acceleration entirely). The error message has change due to some refactoring ("ssh_dispatch_run_fatal: Connection to [...] port 22: message authentication code incorrect") but it means the same thing. -- You are receiving this mail because: You are the assignee for the bug. You are watching someone on the CC list of the bug. _______________________________________________ openssh-bugs mailing list [email protected] https://lists.mindrot.org/mailman/listinfo/openssh-bugs
