From Newsgroup: alt.os.linux.slackware

I have two computers each running Slack 15.0, call them A and B.
I can ssh from A to B, but not from B to A. In the latter
case I get this error message:
ssh: symbol lookup error: ssh: undefined symbol: OPENSSL_add_all_algorithms_noconf

Computer A can ssh and scp to all the computers on my network,
not all of which are running Slackware (those that don't run Raspian instead).

Computer B cannot ssh to any other computer on the network.

I have used slackpkg upgrade once on computer A after the
initial installation. I have used the upgrade on computer
B at least two times, so the specific packages for openssh
and openssl are different.

I have removed and re-installed the openssh and openssl
packages on computer B, but the error persists.

Running on computer A, I can ssh a command to computer
B to scp files on B back to A, and that works.

I have sent all the ssh and ssl config files from computer
A to computer B, so the problem isn't a difference in
the config files.

I can't find the OPENSSL.... anywhere in any of the files
in the /etc/directory on A or B, or in the executables in /usr/bin on B.

Finally, I can ssh from A to itself, but not from B to itself.

After having read all this, If you have any idea of what
I can do to fix the problem please give me a hint.

Thanks.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

root <NoEMail@home.org> wrote:

I have removed and re-installed the openssh and openssl
packages on computer B, but the error persists.

Did you reinstall the openssl-solibs-1.1.1m-x86_64-1 package as well?

Openssl is two packages on Slackware:

openssl-1.1.1m-x86_64-1
openssl-solibs-1.1.1m-x86_64-1

The error you are getting sounds like a runtime linking error, implying
you have the wrong 'solibs' package installed on B.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

On Thu, 9 Jan 2025 21:52:22 -0000 (UTC), root wrote:

I have two computers each running Slack 15.0, call them A and B.
I can ssh from A to B, but not from B to A. In the latter case I get
this error message:
ssh: symbol lookup error: ssh: undefined symbol: OPENSSL_add_all_algorithms_noconf

None of the OpenSSH versions included in Slackware 15 use OPENSSL_add_all_algorithms

OpenSSL versions included with Slackware 15 also seem to have never
included that function (the symbol is just missing, vs copies I checked
from Slackware 14.2..)

In fact, OPENSSL_add_all_algorithms_noconf is no longer a function at all
in versions of OpenSSL included with Slackware 15.. it's a macro in evp.h

You're doing something weird that you're not telling us..
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

Rich <rich@example.invalid> wrote:

root <NoEMail@home.org> wrote:

I have removed and re-installed the openssh and openssl
packages on computer B, but the error persists.

Did you reinstall the openssl-solibs-1.1.1m-x86_64-1 package as well?

Openssl is two packages on Slackware:

openssl-1.1.1m-x86_64-1
openssl-solibs-1.1.1m-x86_64-1

The error you are getting sounds like a runtime linking error, implying
you have the wrong 'solibs' package installed on B.

Thanks for responding. On what I called the B machine: openssl-1.1.1zb-x86_64-1_slack15.0 openssl-solibs-1.1.1zb-x86_64-1_slack15.0

On the A machine:
openssl-1.1.1w-x86_64-1_slack15.0 openssl-solibs-1.1.1w-x86_64-1_slack15.0

So the solibs package has been updated.

It turns out, that I can use ssh from machine A on B, but
there are still other things that don't work on B.

As you can see, the solibs version I have is not what you have.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

Alexander Grotewohl <alexm0n@gmail.com> wrote:

On Thu, 9 Jan 2025 21:52:22 -0000 (UTC), root wrote:

I have two computers each running Slack 15.0, call them A and B.
I can ssh from A to B, but not from B to A. In the latter case I get
this error message:
ssh: symbol lookup error: ssh: undefined symbol:
OPENSSL_add_all_algorithms_noconf

None of the OpenSSH versions included in Slackware 15 use OPENSSL_add_all_algorithms

OpenSSL versions included with Slackware 15 also seem to have never
included that function (the symbol is just missing, vs copies I checked
from Slackware 14.2..)

In fact, OPENSSL_add_all_algorithms_noconf is no longer a function at all
in versions of OpenSSL included with Slackware 15.. it's a macro in evp.h

You're doing something weird that you're not telling us..

That explains why I can't find the text of the error message
anywhere.

There isn't much that I could have done that is special.
I started with a completely new install of 15.0 on an
empty partition. I then copied from 14.2 stuff from my
old source files directory, and recompiled those.
Exactly what I did on my A machine, but on that machine
many of the source files are different. At that stage
on the A machine I did a slackpkg update. I waited
several months before converting the B machine from
14.2. After the intial steps on the B machine, I again
ran the slackpkg update, but now the new stuff was a
later generation from what I have on the A machine.
It was at this point that I found things on the B
machine were not working.

I have been running Slackware since Soft Landing Systems
shutdown. I think my first version of Slackware was
0.89. Nothing on any my my Intel chip systems has
ever run anything but Slackware since.

The OPENSSL.... stuff came from some early version
of Slack, but I can't imagine what I did to cause it.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

root <NoEMail@home.org> wrote:

Rich <rich@example.invalid> wrote:

root <NoEMail@home.org> wrote:

I have removed and re-installed the openssh and openssl
packages on computer B, but the error persists.

Did you reinstall the openssl-solibs-1.1.1m-x86_64-1 package as well?

Openssl is two packages on Slackware:

openssl-1.1.1m-x86_64-1
openssl-solibs-1.1.1m-x86_64-1

The error you are getting sounds like a runtime linking error, implying
you have the wrong 'solibs' package installed on B.

Thanks for responding. On what I called the B machine: openssl-1.1.1zb-x86_64-1_slack15.0 openssl-solibs-1.1.1zb-x86_64-1_slack15.0

On the A machine:
openssl-1.1.1w-x86_64-1_slack15.0 openssl-solibs-1.1.1w-x86_64-1_slack15.0

Put in a little effort to make the B machine contain the same version
of the packages as the A machine (since IIRC you indicate the A machine
is working properly). Then restart ssh (or just reboot) and see if the
issues go away.

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

root <NoEMail@home.org> wrote:

Alexander Grotewohl <alexm0n@gmail.com> wrote:

On Thu, 9 Jan 2025 21:52:22 -0000 (UTC), root wrote:

I have two computers each running Slack 15.0, call them A and B. I
can ssh from A to B, but not from B to A. In the latter case I get
this error message:
ssh: symbol lookup error: ssh: undefined symbol:
OPENSSL_add_all_algorithms_noconf

None of the OpenSSH versions included in Slackware 15 use
OPENSSL_add_all_algorithms

OpenSSL versions included with Slackware 15 also seem to have never
included that function (the symbol is just missing, vs copies I
checked from Slackware 14.2..)

In fact, OPENSSL_add_all_algorithms_noconf is no longer a function
at all in versions of OpenSSL included with Slackware 15.. it's a
macro in evp.h

You're doing something weird that you're not telling us..

That explains why I can't find the text of the error message
anywhere.

There isn't much that I could have done that is special. I started
with a completely new install of 15.0 on an empty partition. I then
copied from 14.2 stuff from my old source files directory, and
recompiled those. Exactly what I did on my A machine, but on that
machine many of the source files are different. At that stage on the
A machine I did a slackpkg update. I waited several months before converting the B machine from 14.2. After the intial steps on the B machine, I again ran the slackpkg update, but now the new stuff was a
later generation from what I have on the A machine. It was at this
point that I found things on the B machine were not working.

So the A was a fresh install of 15, but B was an "upgrade" from a prior
14.2 install? Don't you think that little tidbit of information might
have been useful to have included in your first post?

In which case, your best course of action will likely be:

Reinstall afresh 15.0 onto B, then copy/compile the custom items you
want to add. At which point you should have a B that works properly.

I have been running Slackware since Soft Landing Systems shutdown. I
think my first version of Slackware was 0.89.

In which case you should have well learned enough to fix this glitch
all by yourself without asking anyone anything.

The OPENSSL.... stuff came from some early version of Slack, but I
can't imagine what I did to cause it.

Sounds like you might have installed some 14.2 packages onto B's 15
install (or the update from 14.2 to 15 borked and left some 14.2 cruft
behind that should have gone away instead.

A fresh, new, install of 15 on B is probably the best way to clear up
the issue.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

Put in a little effort to make the B machine contain the same version
of the packages as the A machine (since IIRC you indicate the A machine
is working properly). Then restart ssh (or just reboot) and see if the issues go away.

The problem wasn't Slackware. When I went to bed last night,
the B machine was running perfectly. The B machine runs 24/7.
When I got up this morning, the prompt and path of the B
machine had changed. I run screen on the B machine, and
when I came back to where I left off things had changed.

I went out to Best Buy this morning and bought a new
ssd. I have installed the original version of 15.0 and
so far, everything is running again.

Thanks for your help Rich.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

So the A was a fresh install of 15, but B was an "upgrade" from a prior
14.2 install? Don't you think that little tidbit of information might
have been useful to have included in your first post?

No, that's not what I meant to say. Using the same USB install disk
that I used for the original install on A, I installed 15.0 on
machine B. I installed some of my stuff from source on B, and
ran the machine for a while. Then I upgraded the packages on B.
Thereafter the problems started.

Reinstall afresh 15.0 onto B, then copy/compile the custom items you
want to add. At which point you should have a B that works properly.

Did that this morning.

In which case you should have well learned enough to fix this glitch
all by yourself without asking anyone anything.

Perhaps. I asked for help after everything I tried failed.
As I mention in the previous response, the problem seems
to have been in the drive. It was a 1TB Samsung 870 EVO, with
two equal partitions. I had previously had 14.2 on both partitions.
I reformatted the first partition before starting the install.

The OPENSSL.... stuff came from some early version of Slack, but I
can't imagine what I did to cause it.

Sounds like you might have installed some 14.2 packages onto B's 15
install (or the update from 14.2 to 15 borked and left some 14.2 cruft behind that should have gone away instead.

A fresh, new, install of 15 on B is probably the best way to clear up
the issue.

I already agreed to that, and have done so.

Thanks again Rich.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

root <NoEMail@home.org> wrote:

<<snip>>
As I mention in the previous response, the problem seems
to have been in the drive. It was a 1TB Samsung 870 EVO, with
two equal partitions.
<<snip>>
Thanks again Rich.

Isn't that a "SMART" disk? See man smartctl and the disk
itself should tell you if it's okay, or else what's wrong
with it. I had a 2TB hdd fail a while ago, but a week or two
before it died, messages started displaying during boot
that warned me it was about to die. Gave me plenty of time
to do several extra backups of everything (and rsync -c them
against earlier backups just to double-check), and to buy
a replacement hdd. Hadn't been aware of SMART and smartctl
before that, but now I regularly use smartctl to check disks.
--
John Forkosh
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

root <NoEMail@home.org> wrote:

Put in a little effort to make the B machine contain the same version
of the packages as the A machine (since IIRC you indicate the A machine
is working properly). Then restart ssh (or just reboot) and see if the
issues go away.

The problem wasn't Slackware. When I went to bed last night,
the B machine was running perfectly. The B machine runs 24/7.
When I got up this morning, the prompt and path of the B
machine had changed. I run screen on the B machine, and
when I came back to where I left off things had changed.

I went out to Best Buy this morning and bought a new
ssd. I have installed the original version of 15.0 and
so far, everything is running again.

Thanks for your help Rich.

The news SSD didn't fix the problem. Now I think it was
a motherboard failure. The sata 1 port on the ASUS MB
failed. This is now the third of the six sata ports
that have failed. I got the system up and running,
but I went out and bought the makings of a new system
at Microcenter yesterday.
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: alt.os.linux.slackware

John Forkosh <forkosh@internet.com> wrote:

root <NoEMail@home.org> wrote:

<<snip>>
As I mention in the previous response, the problem seems
to have been in the drive. It was a 1TB Samsung 870 EVO, with
two equal partitions.
<<snip>>
Thanks again Rich.

Isn't that a "SMART" disk? See man smartctl and the disk
itself should tell you if it's okay, or else what's wrong
with it. I had a 2TB hdd fail a while ago, but a week or two
before it died, messages started displaying during boot
that warned me it was about to die. Gave me plenty of time
to do several extra backups of everything (and rsync -c them
against earlier backups just to double-check), and to buy
a replacement hdd. Hadn't been aware of SMART and smartctl
before that, but now I regularly use smartctl to check disks.

Yes it is/was a smart disk, and the only errors reported
were from years ago, and all those were checksum errors
on booting. It only cost me $100 for a news SSD, and they
are always useful. See me my previous post revealing
that, most likely so far, it was a motherboard problem.

Thanks for responding.
--- Synchronet 3.21d-Linux NewsLink 1.2