Date: Mon, 25 Dec 2023 17:04:47 -0800 From: Mark Millard <marklmi@yahoo.com> To: bob prohaska <fbsd@www.zefox.net> Cc: Joseph Holsten <joseph@josephholsten.com>, ticso@cicely.de, Marcin Cieslak <saper@saper.info>, freebsd-arm@freebsd.org Subject: Re: USB-serial adapter suggestions needed Message-ID: <5B6EE00A-3E69-4EEC-BB66-259EC9833841@yahoo.com> In-Reply-To: <ZYm/z3O1zoxU0SZB@www.zefox.net> References: <ZYd%2Bmid70Sc1xg//@www.zefox.net> <snq8819p-3q19-o239-7op5-sss807q66082@fncre.vasb> <ZYeDi2H754ZKyJG3@www.zefox.net> <16864054-4os0-pq3p-7qp0-7299666908os@fncre.vasb> <ZYhSYNxHcmR2I/YP@www.zefox.net> <ZYhjzPLUBT74EVau@cicely7.cicely.de> <ZYiI7KuPwabExucl@www.zefox.net> <50011576-256a-4425-9091-7ddcf0c1085b@app.fastmail.com> <ZYm/z3O1zoxU0SZB@www.zefox.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Dec 25, 2023, at 09:45, bob prohaska <fbsd@www.zefox.net> wrote: > On Sun, Dec 24, 2023 at 01:31:56PM -0800, Joseph Holsten wrote: >> Okay you all, where should all this great info go in the docs? >=20 > Probably under the heading of "inexplicable miscellany" 8-) >=20 > In the meantime there's been a new development, maybe. >=20 > Overnight all four of my ft232 usb-serial sessions dropped their ssh > connections. In addition, one session using pl2303 dropped also, the > two remaining pl2303 sessions remained up. >=20 > On trying to reconnect via ssh to the host using the pl2303 adapter, > the first connection worked with a long authentication delay but a > second connection reported >=20 > bob@ns2:~ % top > Corrupted MAC on input. > ssh_dispatch_run_fatal: Connection to 50.1.20.30 port 22: message = authentication code incorrect Are there other historical examples of usch messages shown by: # more /var/log/auth.log FYI: # ssh -Q mac you have mail hmac-sha1 hmac-sha1-96 hmac-sha2-256 hmac-sha2-512 hmac-md5 hmac-md5-96 umac-64@openssh.com umac-128@openssh.com hmac-sha1-etm@openssh.com hmac-sha1-96-etm@openssh.com hmac-sha2-256-etm@openssh.com hmac-sha2-512-etm@openssh.com hmac-md5-etm@openssh.com hmac-md5-96-etm@openssh.com umac-64-etm@openssh.com umac-128-etm@openssh.com When I looked I saw references to system load being an issue and switching from the likes of a more expensive: hmac-sha1-etm@openssh.com to: umac-64-etm@openssh.com solving that message and such broken pipe issues for at least some contexts. # ssh -vvvv NODEID apparently reports what is used in its debug output. You might try something analogous to: # ssh -o macs=3Dumac-64-etm@openssh.com = <mailto:macs=3Dumac-64-etm@openssh.com> NODEID Apparently one can use MACs lines in /etc/ssh/sshd_config to control what is used by default. NOTE: I'm not expert in this. https://en.wikipedia.org/wiki/UMAC = reports: QUOTE A specific type of UMAC, also commonly referred to just UMAC, is = specified in RFC 4418, it has provable cryptographic strength and is = usually a lot less computationally intensive than other MACs. UMAC's = design is optimized for 32-bit architectures with SIMD support, with a = performance of 1 CPU cycle per byte (cpb) with SIMD and 2 cpb without = SIMD. A closely related variant of UMAC that is optimized for 64-bit = architectures is given by VMAC, which has been submitted to the IETF as = a draft (draft-krovetz-vmac-01) but never gathered enough attention for = becoming a standardized RFC. END QUOTE There may be better macs=3D??? alternatives for the RPi2B v1.1 for all I = know. > This host is a Pi2v1.1 armv7 running 12.4-STABLE FreeBSD 12.4-STABLE = r373269 GENERIC arm >=20 > Re-try was successful, but I've never seen that error message before, = does anybody > recognize it? >=20 > Three of the four restored ftdi sessions had garbage characters mixed = up with the login > prompt, one was clean and the restored pl2303 session was clean. >=20 > The two pl2303 sessions that remained connected showed no upset of any = kind. =3D=3D=3D Mark Millard marklmi at yahoo.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5B6EE00A-3E69-4EEC-BB66-259EC9833841>