Compile OpenSSL okay, OpenSSH breaks

[rharder]

I pieced together how to compile and install openssl. It boils down to these commands:

% [b]./Configure rhapsody-ppc-cc --prefix=/usr/local \
    --openssldir=/usr/local/openssl threads[/b]
% [b]sudo cp -r -L include/openssl /usr/local/include/openssl[/b]
% [b]sudo mv /usr/bin/openssl /usr/bin/openssl_old[/b]
% [b]sudo ln -s /usr/local/bin/openssl /usr/bin/openssl[/b]

You have to copy the include files separately because the installer only installs symbolic links to files that don't exist. Go figure.

Now you can compile OpenSSH 3.0.x, but when I try to 'sudo make install' it, ssh-keygen is unable to make host keys. Also the new ssh program crashes with a "Bus error".

Anyone get any further than this?

Incidentally, I've posted directions for what I know so far at http://iharder.net/macosx/openssh3.html

-Rob

 

[jimr]

I am looking for my notes on this and there is a parallel thread on this here which some of the openssh301

answers lie,

compiling open ssl correctly is more complicated than you suggest and therefore you have problems.

I seem to recall that threads specifically will not work, but that may have been another package.

???


The main hints can be found by cribbing a bit from Chris Pfisterer of FINK fame.
if you read through the package info and the corresponding patches, you can get a goot clue as to what to do.

unfortunately, OSX is getting farther away from rhapsody.
you will have to put a darwin entry in the configure file and threads are not supported.

additionally you will have to teach the make files how to actually build a shared library as a dylib.

if you want some hints about the conpiler flags which you might nedd otherwise, you will have to download a bit of various stuff from the Darwin Apple site and see how those guys fixed things.

The big question is... what about the OpenSSL guys... they should write the configure to correctly ID MacOSX or darwin..



anyway, I did all of these things and my installation runs as well as before....

I can drop the patch files to anyone who replies privately with valid email(no yahoo).

 

[rharder]

I'm not aware of any issues with threads and openssl on OS X, but you can always configure it without the 'threads' option.

In any event it compiles fine--at least, it doesn't report any errors! =)

There's still the problem with the actualy 'ssh' program and 'ssh-keygen' program. 'Dunno what's up with that.

-Rob

 

[jimr]

and libssl
needs to be built as a dylib.

otherwise, I doubt that ssh301 is finding what it expects.

can you get results from openssl when you invoke it from the command line?

a successful compile maens all the symbols became happy with each other.

I wonder what the system thinks about that happiness. *****bus error*****

 

[rharder]

I do have success calling openssl from the command line and getting md5 hashes for instance.

You're right that there may be some other library that OpenSSH 3 was expecting, but you'd think it simply wouldn't compile if it was missing something, not compile and then get a "Bus error."

Ya never know.

-Rob