openssl & openssh inconsistency?

[Stefan Jeglinski]

I installed openssh-3.1p1-2 from the YDL updates directory. There was 
no openssl there so I installed openssl-0.9.6-9. The latter installed 
libcrypto.so.1 and created a symlink 
libcrypto.so.1->libcrypto.so.0.9.6. All was well and good.

Now I'm trying to rebuild netatalk-1.5.2-1a from YDL 2.2 source RPMS, 
and it needs openssl-devel. Fine, so I look in the YDL 2.2 sources 
and I see the same openssh-3.1p1-2 I already installed, and 
openssl-0.9.6b-8, which I assume is "matched" to the openssh.

So I rebuild openssl-0.9.6b-8 to get the devel rpm. Again all works.

Now the punchline. When I try to install my newly rebuilt 
openssl-0.9.6b-8 rpms,  I get

libcrypto.so.1 is needed by openssh-clients-3.1p1-2
libcrypto.so.1 is needed by openssh-3.1p1-2
libcrypto.so.1 is needed by openssh-server-3.1p1-2


Of course libcrypto.so.1 is there, put in by openssl-0.9.6-9. But I 
see that openssl-0.9.6b-8 will install libcrypto.so.0.9.6b, not 
another libcrypto.so.1.

If anyone is still with me (hopefully Dan), can you clear up this 
whole libcrypto.so.* mess? This has confused me before. It seems like 
openssh-3.1 is at odds with openssl-0.9.6b-8. Furthermore, 
openssl-0.9.6-9 installs so.1, which sounds later than so.0.9.6b, and 
yet the -9 openssl package never wants to install over the b package 
because rpm says the b package is newer.

I usually figure this stuff out sooner or later by forcing things, 
but I don't like that, and it's tedious to follow.

Dan, can you clear this up?


Stefan Jeglinski