On Fri, 22 Nov 2019 at 01:25, [email protected] <[email protected]> wrote: > I think, I've found a bug in OpenBSD and it seems, it exists since 6.5. > When I try to scp several archives (OpenBSD install files) from one > BSD-Machine to another, I get on client side the error: [...] > [...] sshd[20245]: ssh_dispatch_run_fatal: Connection from user root > 10.69.0.15 port 5835: message authentication code incorrect
It's not a bug in scp. It's possible that it's a bug in OpenSSH or OpenBSD but unlikely. The message means that the data was changed in transit between client and server causing SSH's integrity check to fail. A large number of things have been found over the years to be causes of this, including faulty/buggy network equipment, ram, ethernet interfaces and network drivers. Many of the known causes are listed here: https://bugzilla.mindrot.org/show_bug.cgi?id=845 > /usr/sbin/sshd -ddd -p 50 -E sshd.debug.4.log If you add "-e" to the command line you'll get more information from after when sshd re-execs itself. > The controller is a virtual machine on ESXi. This is the first variable I'd try removing if possible. There have been other cases of VMWare networking causing problems (although not these symptoms): https://marc.info/?l=openssh-unix-dev&m=153535111501535&w=2 from the dmesg: > em0 at pci2 dev 0 function 0 "Intel 82545EM" rev 0x01: Alternatively, I'd try switch the network interface to vio from em. -- Darren Tucker (dtucker at dtucker.net) GPG key 11EAA6FA / A86E 3E07 5B19 5880 E860 37F4 9357 ECEF 11EA A6FA (new) Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
