Help! SSH is returning the following error message:
OpenSSL version mismatch. Built against 90581f, you have 90602f
How can I correct this?
Help! SSH is returning the following error message:
OpenSSL version mismatch. Built against 90581f, you have 90602f
How can I correct this?
By the way, I did download OpenSSH 3.1, which was just released on Thursday, but I have no idea what do do with it. The command line
./install
does nothing, and the command line
sh install-sh
runs into trouble with the "C compiler." Does anyone out there have the foggiest notion of what's going on? As far as I know, my system has all of FreeBSD 4.4 as part of its subsystem, so these scripts/programs/whatever shouldn't have trouble, right?[b]
Do you have the latest GNU compiler (GCC) installed?
I'm guesing not. I've got a mostly stock Mac OS X 10.1.3. How can I check?
IMHO ....
Actually if you are running FreeBSD, the easiest way to do these kinds of updates is to synchronize your ports tree.
Here are some instructions on how to do that.
After that you simply do:
cd /usr/ports/security/openssh
make
make install
make clean
And you should be all set (assuming that your DSA/RSA and host keys were already configured).
Of course, if you have problems with compilation, you also may have to update your gcc which I believe is under /ports/lang (I am not 100% sure, but since you have 4.4, you should be fairly current on gcc).
One more thing to look for: old crypto files, they may be
lurking around under /usr/lib.
Good Luck! Of course, remember to come back and share with us your solutions ![]()
D'oh! The below was pasted from the command line:
[msp-??-???-??:~] root# cd /usr/ports/security/openssh
/usr/ports/security/openssh: No such file or directory.
[msp-??-???-??:~] root# cd /usr
[msp-??-???-??:~] root# cd /usr/ports
/usr/ports: No such file or directory.
No ports directory! 
OK that's no problem, you can just create /usr/ports as root yourself and follow the link I suggested to download and build (if you wish).
Again, the assumption is that you have a FreeBSD Unix machine, the procedures for an OSX install may be somewhat different.
Also, check to ensure that you do not have 2 different versions of libcrypto libraries, it may be picking up the old one.
/usr/ports/ssh now exists. Stay tuned.
Do the make commands need to be followed by a file path such as
make /users/[username]/desktop/ssh
which is the directory where the ssh components are?
Sorry for all the questions--I'm a UNIX virgin, even though I used to sit in front of an Oracle 7.3.4 on AIX 4.1.3 box. I only used Oracle commands, not UNIX.
Sorry that's not what I meant, when I said that a ports tree needs to exist on your machine. I am not sure how things work on an OSX machine.
You have to use "cvsup" program to build your entire ports subdirectory and then you automatically get /usr/ports/security/openssh.
Again click on this link for directions on how to do that. I am assuming that you ARE Unix savvy. Maybe we should take all this offline with you posting an outcome at the end ![]()
A Unix virgin
Now that's a new one that I have not heard until now.
In the humble opinion of, well, anyone, does the following directory contain the current GNU Compiler for BSD 4.4? If so, which one?
Go here
http://www.macosx.org/utilsys.html
download the patch (I believe it to be the updated version for your OSX install
Run the command it gives you at the site under the download for the patch
Be happy with OSX.
If you really want to get crazy with OSX, get another box and put Darwin on it, there are a TON of cool things to do with the underlying OS without the constraints placed on you by Aqua. There is GCC and all the rest, and if you aren't comfy with the patch because of the source, please go to apple.com and check under the OSX area for the latest news on the SSH bug, they are usually pretty good and happy to help (in a general sort of customer-on-my-webiste sort of way).
gratzi,
loadc
Finally something in UNIX that actually RUNS. Not to say that it fixed the problem, but it actually DID something when I typed in the command line. Not to be hypercritical of the system, but does anyone know how to install the GCC and SSH? When I type in ./install, I get a message saying that permission was denied, even if I'm running the Terminal application as root; ./configure runs fine until it tries to use cc to create an executable; then it tells me that cc can't do that. People, I really am very interested in this sort of thing, and appreciate every bit of information I can get my hands on. I'm frustrated by the fact there is NO novice-level information available regarding specific, well, archives, or whatever the appropriate term is for the files I've downloaded.
Web sites and downloads and GNUs, oh my! Anyone with an SSH build mismatch should go directly to
The SSH package (for non-Mac types, this is a native Macintosh file which will install directly with Apple's Installer.app) was the last one on the above page when I was there; if it's not there, search the site. Also on a Macintosh note, Sherlock.app did an astoundingly effecient job of finding the above site from the search string "Precompiled SSH for OS X." Happy trails!
http://macosx.forked.net/ has tons of precompiled Mac OS X packages. Some are the second or third most recent, but many are the newest stable releases. All of the files decompress as packages; just double click on them to launch Installer.app.
If you love MAC OS X.... check out this vB style for this site, just added today for your pleasure:
Neo
I was thinking of doing just that! I am looking to get a used Mac (wish Mac hardware was like intel ... you buy parts and build your own box). What would you recommend for a decent speed box that would run OSX comfortably!
Neo, I like the lighter look of the site, it is quite pleasant.
Thanks.... running these boards is a lot of work...... believe me, a thankless, time consuming job..... ![]()
Thanks, guys, for everything. I think that, for right now, the site with the precompiled packages is about my speed. Not all of them worked, but the biggies---OpenSSH, pico, tar, and apache--did. The straight BSD command-line programs are MUCH more straightforward than the X11 apps. Of course, the Cocoa (that's OS X's advanced object-oriented application environment, basically OpenStep 2002) applications are the slickest I've ever seen on any platform, but you've got to compare apples to apples (pun intended). Anyhoo, I'm fine with SSH, which I actually use; the GCC can wait until I have more seat time in. Thanks again!