Re: ssh_dispatch_run_fatal: incorrect signature
Sergio Had <[email protected]> Fri, 1 Nov 2024 16:15:05 +0800
| Newsgroups | gmane.os.openbsd.ppc |
|---|---|
| Message-ID | <dc761a4f-2124-40ca-a6ef-0a33bdc4b1b7@Spark> |
--67248e16_1dbd9e74_1c27 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Is the bug OpenBSD-specific by the way or does it affect OpenSSH on all BE platforms? Sergey Fedorov On Nov 1, 2024 at 12:35 +0800, George Koehler <[email protected]>, wrote: > An errata from October 29, 2024 for OpenBSD 7.6 fixed a problem with > OpenSSH on big-endian platforms (like macppc and powerpc64), > > https://www.openbsd.org/errata76.html > > If a big-endian machine doesn't have the errata fix, ssh might fail > with an error, > > $ ssh 192.168.0.112 > ssh_dispatch_run_fatal: Connection to 192.168.0.112 port 22: incorrect signature > > One can work around the problem by removing mlkem768x25519-sha256 from > KexAlgorithms, > > $ ssh -o KexAlgorithms='-mlkem*' 192.168.0.112 > --67248e16_1dbd9e74_1c27 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline <html xmlns=3D=22http://www.w3.org/1999/xhtml=22> <head> <title></title> </head> <body> <div name=3D=22messageBodySection=22> <div dir=3D=22auto=22>Is the bug OpenBSD-specific by the way or does it a= ffect OpenSSH on all BE platforms=3F</div> </div> <div name=3D=22messageSignatureSection=22><br /> Sergey =46edorov</div> <div name=3D=22messageReplySection=22>On Nov 1, 2024 at 12:35 +0800, Geor= ge Koehler <kernigh=40gmail.com>, wrote:<br /> <blockquote type=3D=22cite=22 style=3D=22border-left-color: grey; border-= left-width: thin; border-left-style: solid; margin: 5px 5px;padding-left:= 10px;=22>An errata from October 29, 2024 for OpenBSD 7.6 fixed a problem= with<br /> OpenSSH on big-endian platforms (like macppc and powerpc64),<br /> <br /> https://www.openbsd.org/errata76.html<br /> <br /> If a big-endian machine doesn't have the errata fix, ssh might fail<br />= with an error,<br /> <br /> =24 ssh 192.168.0.112<br /> ssh=5Fdispatch=5Frun=5Ffatal: Connection to 192.168.0.112 port 22: incorr= ect signature<br /> <br /> One can work around the problem by removing mlkem768x25519-sha256 from<br= /> KexAlgorithms,<br /> <br /> =24 ssh -o KexAlgorithms=3D'-mlkem*' 192.168.0.112<br /> <br /></blockquote> </div> </body> </html> --67248e16_1dbd9e74_1c27--