Mailing List Archive

[Bug 845] Received disconnect from ???: 2: Corrupted MAC on input.
https://bugzilla.mindrot.org/show_bug.cgi?id=845

--- Comment #21 from Darren Tucker <dtucker@dtucker.net> ---
Another thing found to cause this in at least one case: ssh's
hardware-accelerated GCM (aes128-gcm@openssh.com) running on the same
CPU (a Xeon E5-2620 v4) as a hardware-accelerated sha1sum process.
Switching the ssh session to chacha20-poly1305@openssh.com 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
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 845] Received disconnect from ???: 2: Corrupted MAC on input. [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=845

Damien Miller <djm@mindrot.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |djm@mindrot.org

--- Comment #22 from Damien Miller <djm@mindrot.org> ---
Do you know what platform that was? That smells like a kernel bug,
failing to save/restore SSE registers.

--
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
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs
[Bug 845] Received disconnect from ???: 2: Corrupted MAC on input. [ In reply to ]
https://bugzilla.mindrot.org/show_bug.cgi?id=845

--- Comment #23 from Darren Tucker <dtucker@dtucker.net> ---
(In reply to Damien Miller from comment #22)
> Do you know what platform that was? That smells like a kernel bug,
> failing to save/restore SSE registers.

It's a Linux of some flavour, but it's one of many similar machines and
it's the only one affected, and it seems at least somewhat sensitive to
which cpu core the sha1sum schedules on, so my bet would be a faulty
CPU.

--
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
openssh-bugs@mindrot.org
https://lists.mindrot.org/mailman/listinfo/openssh-bugs