Date: Wed, 29 Dec 2004 16:51:02 -0500 (EST) From: Jameel Akari <jakari@bithose.com> To: freebsd-alpha@freebsd.org Subject: Re: ssh compatibility question Message-ID: <Pine.OSF.4.61.0412291641350.28806@poptart.bithose.com> In-Reply-To: <0B21C422-59E1-11D9-8453-000393768D2C@mcgillsociety.org> References: <0B21C422-59E1-11D9-8453-000393768D2C@mcgillsociety.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Short answer: Upgrade the SSH on the Tru64 box first. The FreeBSD and OSX included OpenSSH installs are far more up to date and correct. Long answer: Certain older commercial SSH releases had off-by-N bugs in the way that key lengths are calculated. One I still see on some systems is with 1024-bit RSA keys (which many report at 1023 in length, and the client complains. OpenSSH does work on Tru64 (using it right now to type this) and will compile with the ccc compiler just fine, and may be available on the "Internet Solutions" CDROM (though I haven't looked at those in a while. This isn't officially supported by DigiHewPaq, which may or may not matter to you. You may want to force SSHv1 mode with -1 on the FreeBSD machine as well and see if that works - might be a difference in the default ssh_config between it and OSX, or it might be that the v1/v2 negotition blows up. > Will "Mac hmac-md5" fix that problem? It may, but only if the keysize bug isn't also common to the md5 part of the program. -- #!/jameel/akari sleep 4800; make clean && make breakfast
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.OSF.4.61.0412291641350.28806>