Stumped - symbol loockup error: undefined symbol: EVP_idea_cbc

Dan Espen

Crashdamage <03z1krd7@nospam.invalid> writes:

> On Mon, 07 Jan 2008 15:15:16 GMT, Dan Espen
> <.SPAMtelcordia.com> wrote:
>> Crashdamage <03z1krd7@nospam.invalid> writes:
>
>>> On Sun, 06 Jan 2008 17:57:57 -0500, David W. Hodgins
>>> <> wrote:
>>>> On Sun, 06 Jan 2008 17:24:08 -0500, Crashdamage <03z1krd7@nospam.invalid> wrote:
>>>
>>>>> Anyway, OK, the link libcrypto.so takes care of resolving the EVP's.
>>>>> But how do I fix this? There must be a way - it's not like everything
>>>>> is trashed. Seems like it should be fairly simple and doable - if I
>>>>> knew what to do.
>>>
>>>> Looks like the problem may be due to the order the directories are being
>>>> searched. Change /etc/ld.so.conf so that /lib is searched first, followed
>>>> by /usr/lib, followed by anything added by other applications. Then
>>>> run ldconfig, and then confirm with ldd that the correct version of libcrypt
>>>> is being selected.
>>>
>>> My existing ld.so.conf doesn't search /lib at at all, but it hasn't
>>> changed since Feb 2007 either so I don't think that's it. Here it is:
>>>
>>> include ld.so.conf.d/*.conf
>>> /usr/X11R6/lib
>>> /usr/lib/qt3/lib
>>> /opt/win4linpro/lib/sys
>>>
>>> Are you saying I should just add '/lib' to the top of the directory
>>> list? Isn't that too general?
>
>> You could, at least to see what happens.
>> You could also export LD_LIBRARY_PATH to see what that does.
>> But...
>
>>> At present, running '# ldconfig' returns nothing. Honestly, I've never
>>> run that command. What exactly does it do and what should it return?
>
>> Try "man ldconfig".
>> It's normally run when you install a package.
>> Try:
>
>> ldconfig -v
>
>> if you want feedback.
>
> That gave *lots* of feedback...
>
>>> The version of libcrypt installed never changed, and it's still the
>>> original. I carefully rolled all packages I did change back and made
>>> sure only one version (the previous one) was still installed. Still,
>>> *something* is not quite as it was.
>
>> Actually, normal shared library versioning should be protecting you.
>> Perhaps you should post the output of:
>
>> ls -l /usr/lib/libcrypt*
>
> $ ls -l /usr/lib/libcrypt*
> lrwxrwxrwx 1 root root 38 Jan 7 23:38 /usr/lib/libcrypto.so ->
> ../../../../usr/lib/libcrypto.so.0.9.7*
> -rwxr-xr-x 1 root root 1038480 Oct 10 2005
> /usr/lib/libcrypto.so.0.9.7*
> lrwxrwxrwx 1 root root 33 Jan 7 23:38 /usr/lib/libcrypt.so ->
> ../../../../lib/libcrypt-2.3.3.so*
>
> Some of the above are very recent because I've been replacing stuff from
> backups tonight trying to make sure everything is rolled back to
> *exactly* as it was before all this started.
>
>> ls -l /opt/win4linpro/lib/sys/libcrypt*
>
> $ ls -l /opt/win4linpro/lib/sys/libcrypt*
> -r--r--r-- 1 root bin 1029704 Dec 4 13:25
> /opt/win4linpro/lib/sys/libcrypto.so.0.9.7

So both libcrypto.so files are version 0.9.7
but one has EVP_idea_cbc and the other doesn't.
Somebody screwed up.

I think I'd remove the win4lin library from your ld.so
and use a script to start win4lin that sets LD_LIBRARY_PATH.

Crashdamage

On Mon, 07 Jan 2008 15:15:16 GMT, Dan Espen
<.SPAMtelcordia.com> wrote:
> Crashdamage <03z1krd7@nospam.invalid> writes:

>> On Sun, 06 Jan 2008 17:57:57 -0500, David W. Hodgins
>> <> wrote:
>>> On Sun, 06 Jan 2008 17:24:08 -0500, Crashdamage <03z1krd7@nospam.invalid> wrote:
>>
>>>> Anyway, OK, the link libcrypto.so takes care of resolving the EVP's.
>>>> But how do I fix this? There must be a way - it's not like everything
>>>> is trashed. Seems like it should be fairly simple and doable - if I
>>>> knew what to do.
>>
>>> Looks like the problem may be due to the order the directories are being
>>> searched. Change /etc/ld.so.conf so that /lib is searched first, followed
>>> by /usr/lib, followed by anything added by other applications. Then
>>> run ldconfig, and then confirm with ldd that the correct version of libcrypt
>>> is being selected.
>>
>> My existing ld.so.conf doesn't search /lib at at all, but it hasn't
>> changed since Feb 2007 either so I don't think that's it. Here it is:
>>
>> include ld.so.conf.d/*.conf
>> /usr/X11R6/lib
>> /usr/lib/qt3/lib
>> /opt/win4linpro/lib/sys
>>
>> Are you saying I should just add '/lib' to the top of the directory
>> list? Isn't that too general?

> You could, at least to see what happens.
> You could also export LD_LIBRARY_PATH to see what that does.
> But...

>> At present, running '# ldconfig' returns nothing. Honestly, I've never
>> run that command. What exactly does it do and what should it return?

> Try "man ldconfig".
> It's normally run when you install a package.
> Try:

> ldconfig -v

> if you want feedback.

That gave *lots* of feedback...

>> The version of libcrypt installed never changed, and it's still the
>> original. I carefully rolled all packages I did change back and made
>> sure only one version (the previous one) was still installed. Still,
>> *something* is not quite as it was.

> Actually, normal shared library versioning should be protecting you.
> Perhaps you should post the output of:

> ls -l /usr/lib/libcrypt*

$ ls -l /usr/lib/libcrypt*
lrwxrwxrwx 1 root root 38 Jan 7 23:38 /usr/lib/libcrypto.so ->
.../../../../usr/lib/libcrypto.so.0.9.7*
-rwxr-xr-x 1 root root 1038480 Oct 10 2005
/usr/lib/libcrypto.so.0.9.7*
lrwxrwxrwx 1 root root 33 Jan 7 23:38 /usr/lib/libcrypt.so ->
.../../../../lib/libcrypt-2.3.3.so*

Some of the above are very recent because I've been replacing stuff from
backups tonight trying to make sure everything is rolled back to
*exactly* as it was before all this started.

> ls -l /opt/win4linpro/lib/sys/libcrypt*

$ ls -l /opt/win4linpro/lib/sys/libcrypt*
-r--r--r-- 1 root bin 1029704 Dec 4 13:25
/opt/win4linpro/lib/sys/libcrypto.so.0.9.7


> The program in question should be going for a specific version
> of libcrypt and there shouldn't be 2 libraries with the same version
> but different content.

>> At least I'm learning some stuff...thanks!

> A reward in it's own right.

Thanks for trying to help.
--
Registered Linux user #266531

Crashdamage

On Mon, 07 Jan 2008 15:15:16 GMT, Dan Espen
<.SPAMtelcordia.com> wrote:
> Crashdamage <03z1krd7@nospam.invalid> writes:

>> On Sun, 06 Jan 2008 17:57:57 -0500, David W. Hodgins
>> <> wrote:
>>> On Sun, 06 Jan 2008 17:24:08 -0500, Crashdamage <03z1krd7@nospam.invalid> wrote:
>>
>>>> Anyway, OK, the link libcrypto.so takes care of resolving the EVP's.
>>>> But how do I fix this? There must be a way - it's not like everything
>>>> is trashed. Seems like it should be fairly simple and doable - if I
>>>> knew what to do.
>>
>>> Looks like the problem may be due to the order the directories are being
>>> searched. Change /etc/ld.so.conf so that /lib is searched first, followed
>>> by /usr/lib, followed by anything added by other applications. Then
>>> run ldconfig, and then confirm with ldd that the correct version of libcrypt
>>> is being selected.
>>
>> My existing ld.so.conf doesn't search /lib at at all, but it hasn't
>> changed since Feb 2007 either so I don't think that's it. Here it is:
>>
>> include ld.so.conf.d/*.conf
>> /usr/X11R6/lib
>> /usr/lib/qt3/lib
>> /opt/win4linpro/lib/sys
>>
>> Are you saying I should just add '/lib' to the top of the directory
>> list? Isn't that too general?

> You could, at least to see what happens.
> You could also export LD_LIBRARY_PATH to see what that does.
> But...

>> At present, running '# ldconfig' returns nothing. Honestly, I've never
>> run that command. What exactly does it do and what should it return?

> Try "man ldconfig".
> It's normally run when you install a package.
> Try:

> ldconfig -v

> if you want feedback.

That gave *lots* of feedback...

>> The version of libcrypt installed never changed, and it's still the
>> original. I carefully rolled all packages I did change back and made
>> sure only one version (the previous one) was still installed. Still,
>> *something* is not quite as it was.

> Actually, normal shared library versioning should be protecting you.
> Perhaps you should post the output of:

> ls -l /usr/lib/libcrypt*

$ ls -l /usr/lib/libcrypt*
lrwxrwxrwx 1 root root 38 Jan 7 23:38 /usr/lib/libcrypto.so ->
.../../../../usr/lib/libcrypto.so.0.9.7*
-rwxr-xr-x 1 root root 1038480 Oct 10 2005
/usr/lib/libcrypto.so.0.9.7*
lrwxrwxrwx 1 root root 33 Jan 7 23:38 /usr/lib/libcrypt.so ->
.../../../../lib/libcrypt-2.3.3.so*

Some of the above are very recent because I've been replacing stuff from
backups tonight trying to make sure everything is rolled back to
*exactly* as it was before all this started.

> ls -l /opt/win4linpro/lib/sys/libcrypt*

$ ls -l /opt/win4linpro/lib/sys/libcrypt*
-r--r--r-- 1 root bin 1029704 Dec 4 13:25
/opt/win4linpro/lib/sys/libcrypto.so.0.9.7


> The program in question should be going for a specific version
> of libcrypt and there shouldn't be 2 libraries with the same version
> but different content.

>> At least I'm learning some stuff...thanks!

> A reward in it's own right.

Thanks for trying to help.
--
Registered Linux user #266531

David W. Hodgins

On Mon, 07 Jan 2008 06:26:51 -0500, Crashdamage <03z1krd7@nospam.invalid> wrote:

> Are you saying I should just add '/lib' to the top of the directory
> list? Isn't that too general?

Yes, that's what I'm saying. Applications that require there own version
of a system module/library, should use a script to set the LD_PRELOAD environment
variable, to override the default dynamic linking order.

> At present, running '# ldconfig' returns nothing. Honestly, I've never
> run that command. What exactly does it do and what should it return?

It determines which entry points are in which dynamically loaded module,
and updates /etc/ld.so.cache, which is used by ld.so, to determine which
libraries to load, for a given module.

> The version of libcrypt installed never changed, and it's still the
> original. I carefully rolled all packages I did change back and made
> sure only one version (the previous one) was still installed. Still,
> *something* is not quite as it was.

The version of libcrypt being used by win4linpro, is not compatible with
the normal system wide version. It should only be used by win4linpro,
using the LD_PRELOAD environment variable.

> At least I'm learning some stuff...thanks!

The good thing about learning the hard way, is that you never forget, those
lessons.

One thing I've found helpful, is to install and run prelink, and then look
at the log file, to see which applications have missing dependencies. Much
easier then waiting for each application to fail, and then trying to figure
out which dependency is missing.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

Crashdamage

On Sun, 06 Jan 2008 17:57:57 -0500, David W. Hodgins
<> wrote:
> On Sun, 06 Jan 2008 17:24:08 -0500, Crashdamage <03z1krd7@nospam.invalid> wrote:

>> Anyway, OK, the link libcrypto.so takes care of resolving the EVP's.
>> But how do I fix this? There must be a way - it's not like everything
>> is trashed. Seems like it should be fairly simple and doable - if I
>> knew what to do.

> Looks like the problem may be due to the order the directories are being
> searched. Change /etc/ld.so.conf so that /lib is searched first, followed
> by /usr/lib, followed by anything added by other applications. Then
> run ldconfig, and then confirm with ldd that the correct version of libcrypt
> is being selected.

My existing ld.so.conf doesn't search /lib at at all, but it hasn't
changed since Feb 2007 either so I don't think that's it. Here it is:

include ld.so.conf.d/*.conf
/usr/X11R6/lib
/usr/lib/qt3/lib
/opt/win4linpro/lib/sys

Are you saying I should just add '/lib' to the top of the directory
list? Isn't that too general?

At present, running '# ldconfig' returns nothing. Honestly, I've never
run that command. What exactly does it do and what should it return?

The version of libcrypt installed never changed, and it's still the
original. I carefully rolled all packages I did change back and made
sure only one version (the previous one) was still installed. Still,
*something* is not quite as it was.

At least I'm learning some stuff...thanks!

--
Registered Linux user #266531

Dan Espen

Crashdamage <03z1krd7@nospam.invalid> writes:

> On Mon, 07 Jan 2008 15:15:16 GMT, Dan Espen
> <.SPAMtelcordia.com> wrote:
>> Crashdamage <03z1krd7@nospam.invalid> writes:
>
>>> On Sun, 06 Jan 2008 17:57:57 -0500, David W. Hodgins
>>> <> wrote:
>>>> On Sun, 06 Jan 2008 17:24:08 -0500, Crashdamage <03z1krd7@nospam.invalid> wrote:
>>>
>>>>> Anyway, OK, the link libcrypto.so takes care of resolving the EVP's.
>>>>> But how do I fix this? There must be a way - it's not like everything
>>>>> is trashed. Seems like it should be fairly simple and doable - if I
>>>>> knew what to do.
>>>
>>>> Looks like the problem may be due to the order the directories are being
>>>> searched. Change /etc/ld.so.conf so that /lib is searched first, followed
>>>> by /usr/lib, followed by anything added by other applications. Then
>>>> run ldconfig, and then confirm with ldd that the correct version of libcrypt
>>>> is being selected.
>>>
>>> My existing ld.so.conf doesn't search /lib at at all, but it hasn't
>>> changed since Feb 2007 either so I don't think that's it. Here it is:
>>>
>>> include ld.so.conf.d/*.conf
>>> /usr/X11R6/lib
>>> /usr/lib/qt3/lib
>>> /opt/win4linpro/lib/sys
>>>
>>> Are you saying I should just add '/lib' to the top of the directory
>>> list? Isn't that too general?
>
>> You could, at least to see what happens.
>> You could also export LD_LIBRARY_PATH to see what that does.
>> But...
>
>>> At present, running '# ldconfig' returns nothing. Honestly, I've never
>>> run that command. What exactly does it do and what should it return?
>
>> Try "man ldconfig".
>> It's normally run when you install a package.
>> Try:
>
>> ldconfig -v
>
>> if you want feedback.
>
> That gave *lots* of feedback...
>
>>> The version of libcrypt installed never changed, and it's still the
>>> original. I carefully rolled all packages I did change back and made
>>> sure only one version (the previous one) was still installed. Still,
>>> *something* is not quite as it was.
>
>> Actually, normal shared library versioning should be protecting you.
>> Perhaps you should post the output of:
>
>> ls -l /usr/lib/libcrypt*
>
> $ ls -l /usr/lib/libcrypt*
> lrwxrwxrwx 1 root root 38 Jan 7 23:38 /usr/lib/libcrypto.so ->
> ../../../../usr/lib/libcrypto.so.0.9.7*
> -rwxr-xr-x 1 root root 1038480 Oct 10 2005
> /usr/lib/libcrypto.so.0.9.7*
> lrwxrwxrwx 1 root root 33 Jan 7 23:38 /usr/lib/libcrypt.so ->
> ../../../../lib/libcrypt-2.3.3.so*
>
> Some of the above are very recent because I've been replacing stuff from
> backups tonight trying to make sure everything is rolled back to
> *exactly* as it was before all this started.
>
>> ls -l /opt/win4linpro/lib/sys/libcrypt*
>
> $ ls -l /opt/win4linpro/lib/sys/libcrypt*
> -r--r--r-- 1 root bin 1029704 Dec 4 13:25
> /opt/win4linpro/lib/sys/libcrypto.so.0.9.7

So both libcrypto.so files are version 0.9.7
but one has EVP_idea_cbc and the other doesn't.
Somebody screwed up.

I think I'd remove the win4lin library from your ld.so
and use a script to start win4lin that sets LD_LIBRARY_PATH.

Crashdamage

On Sun, 06 Jan 2008 15:41:34 -0500, David W. Hodgins
<> wrote:
> On Sun, 06 Jan 2008 14:55:42 -0500, Crashdamage <03z1krd7@nospam.invalid> wrote:

>>> /usr/lib/libssl.so.0.9.7: undefined symbol: EVP_idea_cbc

> You might want to try the 2008 version, libopenssl0.9.8-0.9.8e-8.1mdv2008.0
> nm -D on that version does not include EVP_idea_cbc.

Hmmm....I dunno about that one. There's a *lot* of dependencies on that
package. I've gotta think that trying to shoehorn in a version that
much newer would likely cause more trouble than I've got now.

Thing is, as far as I can tell I put everything back as it was. But
*something* is still changed. The question is what and how do I fix
that?

Thanks for the help. I appreciate it.

--
Registered Linux user #266531

Dan Espen

Crashdamage <03z1krd7@nospam.invalid> writes:

> On Mon, 07 Jan 2008 15:15:16 GMT, Dan Espen
> <.SPAMtelcordia.com> wrote:
>> Crashdamage <03z1krd7@nospam.invalid> writes:
>
>>> On Sun, 06 Jan 2008 17:57:57 -0500, David W. Hodgins
>>> <> wrote:
>>>> On Sun, 06 Jan 2008 17:24:08 -0500, Crashdamage <03z1krd7@nospam.invalid> wrote:
>>>
>>>>> Anyway, OK, the link libcrypto.so takes care of resolving the EVP's.
>>>>> But how do I fix this? There must be a way - it's not like everything
>>>>> is trashed. Seems like it should be fairly simple and doable - if I
>>>>> knew what to do.
>>>
>>>> Looks like the problem may be due to the order the directories are being
>>>> searched. Change /etc/ld.so.conf so that /lib is searched first, followed
>>>> by /usr/lib, followed by anything added by other applications. Then
>>>> run ldconfig, and then confirm with ldd that the correct version of libcrypt
>>>> is being selected.
>>>
>>> My existing ld.so.conf doesn't search /lib at at all, but it hasn't
>>> changed since Feb 2007 either so I don't think that's it. Here it is:
>>>
>>> include ld.so.conf.d/*.conf
>>> /usr/X11R6/lib
>>> /usr/lib/qt3/lib
>>> /opt/win4linpro/lib/sys
>>>
>>> Are you saying I should just add '/lib' to the top of the directory
>>> list? Isn't that too general?
>
>> You could, at least to see what happens.
>> You could also export LD_LIBRARY_PATH to see what that does.
>> But...
>
>>> At present, running '# ldconfig' returns nothing. Honestly, I've never
>>> run that command. What exactly does it do and what should it return?
>
>> Try "man ldconfig".
>> It's normally run when you install a package.
>> Try:
>
>> ldconfig -v
>
>> if you want feedback.
>
> That gave *lots* of feedback...
>
>>> The version of libcrypt installed never changed, and it's still the
>>> original. I carefully rolled all packages I did change back and made
>>> sure only one version (the previous one) was still installed. Still,
>>> *something* is not quite as it was.
>
>> Actually, normal shared library versioning should be protecting you.
>> Perhaps you should post the output of:
>
>> ls -l /usr/lib/libcrypt*
>
> $ ls -l /usr/lib/libcrypt*
> lrwxrwxrwx 1 root root 38 Jan 7 23:38 /usr/lib/libcrypto.so ->
> ../../../../usr/lib/libcrypto.so.0.9.7*
> -rwxr-xr-x 1 root root 1038480 Oct 10 2005
> /usr/lib/libcrypto.so.0.9.7*
> lrwxrwxrwx 1 root root 33 Jan 7 23:38 /usr/lib/libcrypt.so ->
> ../../../../lib/libcrypt-2.3.3.so*
>
> Some of the above are very recent because I've been replacing stuff from
> backups tonight trying to make sure everything is rolled back to
> *exactly* as it was before all this started.
>
>> ls -l /opt/win4linpro/lib/sys/libcrypt*
>
> $ ls -l /opt/win4linpro/lib/sys/libcrypt*
> -r--r--r-- 1 root bin 1029704 Dec 4 13:25
> /opt/win4linpro/lib/sys/libcrypto.so.0.9.7

So both libcrypto.so files are version 0.9.7
but one has EVP_idea_cbc and the other doesn't.
Somebody screwed up.

I think I'd remove the win4lin library from your ld.so
and use a script to start win4lin that sets LD_LIBRARY_PATH.

Dan Espen

Crashdamage <03z1krd7@nospam.invalid> writes:

> On Sun, 06 Jan 2008 17:57:57 -0500, David W. Hodgins
> <> wrote:
>> On Sun, 06 Jan 2008 17:24:08 -0500, Crashdamage <03z1krd7@nospam.invalid> wrote:
>
>>> Anyway, OK, the link libcrypto.so takes care of resolving the EVP's.
>>> But how do I fix this? There must be a way - it's not like everything
>>> is trashed. Seems like it should be fairly simple and doable - if I
>>> knew what to do.
>
>> Looks like the problem may be due to the order the directories are being
>> searched. Change /etc/ld.so.conf so that /lib is searched first, followed
>> by /usr/lib, followed by anything added by other applications. Then
>> run ldconfig, and then confirm with ldd that the correct version of libcrypt
>> is being selected.
>
> My existing ld.so.conf doesn't search /lib at at all, but it hasn't
> changed since Feb 2007 either so I don't think that's it. Here it is:
>
> include ld.so.conf.d/*.conf
> /usr/X11R6/lib
> /usr/lib/qt3/lib
> /opt/win4linpro/lib/sys
>
> Are you saying I should just add '/lib' to the top of the directory
> list? Isn't that too general?

You could, at least to see what happens.
You could also export LD_LIBRARY_PATH to see what that does.
But...

> At present, running '# ldconfig' returns nothing. Honestly, I've never
> run that command. What exactly does it do and what should it return?

Try "man ldconfig".
It's normally run when you install a package.
Try:

ldconfig -v

if you want feedback.

> The version of libcrypt installed never changed, and it's still the
> original. I carefully rolled all packages I did change back and made
> sure only one version (the previous one) was still installed. Still,
> *something* is not quite as it was.

Actually, normal shared library versioning should be protecting you.
Perhaps you should post the output of:

ls -l /usr/lib/libcrypt*
ls -l /opt/win4linpro/lib/sys/libcrypt*

The program in question should be going for a specific version
of libcrypt and there shouldn't be 2 libraries with the same version
but different content.

> At least I'm learning some stuff...thanks!

A reward in it's own right.

Crashdamage

On Mon, 07 Jan 2008 15:15:16 GMT, Dan Espen
<.SPAMtelcordia.com> wrote:
> Crashdamage <03z1krd7@nospam.invalid> writes:

>> On Sun, 06 Jan 2008 17:57:57 -0500, David W. Hodgins
>> <> wrote:
>>> On Sun, 06 Jan 2008 17:24:08 -0500, Crashdamage <03z1krd7@nospam.invalid> wrote:
>>
>>>> Anyway, OK, the link libcrypto.so takes care of resolving the EVP's.
>>>> But how do I fix this? There must be a way - it's not like everything
>>>> is trashed. Seems like it should be fairly simple and doable - if I
>>>> knew what to do.
>>
>>> Looks like the problem may be due to the order the directories are being
>>> searched. Change /etc/ld.so.conf so that /lib is searched first, followed
>>> by /usr/lib, followed by anything added by other applications. Then
>>> run ldconfig, and then confirm with ldd that the correct version of libcrypt
>>> is being selected.
>>
>> My existing ld.so.conf doesn't search /lib at at all, but it hasn't
>> changed since Feb 2007 either so I don't think that's it. Here it is:
>>
>> include ld.so.conf.d/*.conf
>> /usr/X11R6/lib
>> /usr/lib/qt3/lib
>> /opt/win4linpro/lib/sys
>>
>> Are you saying I should just add '/lib' to the top of the directory
>> list? Isn't that too general?

> You could, at least to see what happens.
> You could also export LD_LIBRARY_PATH to see what that does.
> But...

>> At present, running '# ldconfig' returns nothing. Honestly, I've never
>> run that command. What exactly does it do and what should it return?

> Try "man ldconfig".
> It's normally run when you install a package.
> Try:

> ldconfig -v

> if you want feedback.

That gave *lots* of feedback...

>> The version of libcrypt installed never changed, and it's still the
>> original. I carefully rolled all packages I did change back and made
>> sure only one version (the previous one) was still installed. Still,
>> *something* is not quite as it was.

> Actually, normal shared library versioning should be protecting you.
> Perhaps you should post the output of:

> ls -l /usr/lib/libcrypt*

$ ls -l /usr/lib/libcrypt*
lrwxrwxrwx 1 root root 38 Jan 7 23:38 /usr/lib/libcrypto.so ->
.../../../../usr/lib/libcrypto.so.0.9.7*
-rwxr-xr-x 1 root root 1038480 Oct 10 2005
/usr/lib/libcrypto.so.0.9.7*
lrwxrwxrwx 1 root root 33 Jan 7 23:38 /usr/lib/libcrypt.so ->
.../../../../lib/libcrypt-2.3.3.so*

Some of the above are very recent because I've been replacing stuff from
backups tonight trying to make sure everything is rolled back to
*exactly* as it was before all this started.

> ls -l /opt/win4linpro/lib/sys/libcrypt*

$ ls -l /opt/win4linpro/lib/sys/libcrypt*
-r--r--r-- 1 root bin 1029704 Dec 4 13:25
/opt/win4linpro/lib/sys/libcrypto.so.0.9.7


> The program in question should be going for a specific version
> of libcrypt and there shouldn't be 2 libraries with the same version
> but different content.

>> At least I'm learning some stuff...thanks!

> A reward in it's own right.

Thanks for trying to help.
--
Registered Linux user #266531