openssh bugs - May 2020 - [Bug 3168] New: libssh.a(utf8.o): undefined reference to symbol 'strcasestr@@GLIBC_2.17'

https://bugzilla.mindrot.org/show_bug.cgi?id=3168

            Bug ID: 3168
           Summary: libssh.a(utf8.o): undefined reference to symbol
                    'strcasestr@@GLIBC_2.17'
           Product: Portable OpenSSH
           Version: 8.2p1
          Hardware: ARM64
                OS: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: ssh
          Assignee: unassigned-bugs at mindrot.org
          Reporter: sgowda at altiostar.com

Hi,

I am getting following error while build openssh.

/tools/xilinx/SDK/2019.1/gnu/aarch64/lin/aarch64-linux/bin/aarch64-linux-gnu-ld
-o ssh ssh.o readconf.o clientloop.o sshtty.o sshconnect.o
sshconnect2.o mux.o ssh-sk-client.o
-L/new-home/sukeshg/svnwork/ant-confd/os/../art/os-ant-revi/buildos/openssh/openssh-portable-V_8_2_P1/openbsd-compat/
-lssh -lopenbsd-compat  -lcrypto -ldl -lutil -lz  -lcrypt -lresolv
/tools/xilinx/SDK/2019.1/gnu/aarch64/lin/aarch64-linux/bin/aarch64-linux-gnu-ld:
/new-home/sukeshg/svnwork/ant-confd/os/../art/os-ant-revi/buildos/openssh/openssh-portable-V_8_2_P1/openbsd-compat//libssh.a(utf8.o):
undefined reference to symbol 'strcasestr@@GLIBC_2.17'
/tools/xilinx/SDK/2019.1/gnu/aarch64/lin/aarch64-linux/bin/aarch64-linux-gnu-ld:
/tools/xilinx/SDK/2019.1/gnu/aarch64/lin/aarch64-linux/bin/../aarch64-linux-gnu/libc/lib/libc.so.6:
error adding symbols: DSO missing from command line
make[2]: *** [ssh] Error 1


Can anybody help me resolving this issue.

Regards,
Sukesh.R

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3168

Darren Tucker <dtucker at dtucker.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dtucker at dtucker.net

--- Comment #1 from Darren Tucker <dtucker at dtucker.net> ---
Configure should have detected that you don't have strcasestr.  What is
HAVE_STRCASESTR set to in config.h

There's also something weird about your build environment:
>
/tools/xilinx/SDK/2019.1/gnu/aarch64/lin/aarch64-linux/bin/aarch64-linux-gnu-ld:
/new-home/sukeshg/svnwork/ant-confd/os/../art/os-ant-revi/buildos/openssh/openssh-portable-V_8_2_P1/openbsd-compat//libssh.a(utf8.o):
undefined reference to symbol 'strcasestr@@GLIBC_2.17'
libssh.a lives in the top level directory not openbsd-compat.  How are
you running configure?  Also make sure you don't have a config.h from
another system in the path somewhere.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3168

--- Comment #2 from sukesh gowda <sgowda at altiostar.com> ---
Hi Dareen,

You are correct HAVE_STRCASESTR is set in config.h But when I do a
cross compile its giving error. Because I am doing autoreconf on the
host system(x86) and compiling for ARM64.

Can you please tell me How do I cross compile for a different target
which doesn't support autoconf/autoreconf. Without autoreconf I don't
get configure for file.

Regards,
Sukesh.R

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3168

--- Comment #3 from sukesh gowda <sgowda at altiostar.com> ---
Hi Daren,

Sorry for the previous message, I got confused.
I downloaded a package from
https://github.com/openssh/openssh-portable/releases/V_8_2_P1.tar.gz
Extracted it.
Do autoreconf.
Then run it on docker with cross-compiler settings.
I can see from the log ?checking for strcasestr... yes?
So in config.h I can see 
#define HAVE_STRCASESTR 1

What else could be the reason for undefined reference to symbol
'strcasestr@@GLIBC_2.17'

I was getting few loader errors so moved libssh.a inside openbsd-compat
folder, its just for testing

Regards,
Sukesh.R

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3168

--- Comment #4 from Darren Tucker <dtucker at dtucker.net> ---
(In reply to sukesh gowda from comment #2)
> You are correct HAVE_STRCASESTR is set in config.h But when I do a
> cross compile its giving error. Because I am doing autoreconf on the
> host system(x86) and compiling for ARM64.
How are you configuring it?
> Can you please tell me How do I cross compile for a different target
> which doesn't support autoconf/autoreconf. Without autoreconf I
> don't get configure for file.
[...]
> Sorry for the previous message, I got confused.
> I downloaded a package from
> https://github.com/openssh/openssh-portable/releases/V_8_2_P1.tar.gz
> Extracted it.
> Do autoreconf.
You're downloading the source code by release tag, which is fine but it
doesn't have generated files such as configure.  If you download the
release tarball (eg
https://cdn.openbsd.org/pub/OpenBSD/OpenSSH/portable/openssh-8.2p1.tar.gz)
it'll have them.
> Then run it on docker with cross-compiler settings.
Exactly what "cross-compiler settings"?
> I can see from the log ?checking for strcasestr... yes?
> So in config.h I can see 
> #define HAVE_STRCASESTR 1
> 
> What else could be the reason for undefined reference to symbol
> 'strcasestr@@GLIBC_2.17'
> 
> I was getting few loader errors so moved libssh.a inside
> openbsd-compat folder, its just for testing
Every thing that you do without mentioning it here makes it harder to
figure out what's going on.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3168

--- Comment #5 from sukesh gowda <sgowda at altiostar.com> ---
Hi,

I was able to solve the issue. I changed compiler to
aarch64-linux-gnu-gcc and was able to compile.

I am facing one more problem while connecting to ssh subsystem

fxt23190004 /usr/bin # ssh -s -vv -p 2022 root at 127.0.0.1 netconf
OpenSSH_8.2p1, OpenSSL 1.0.2r  26 Feb 2019
debug2: resolve_canonicalize: hostname 127.0.0.1 is address
debug1: Authenticator provider $SSH_SK_PROVIDER did not resolve;
disabling
debug2: ssh_connect_direct
debug1: Connecting to 127.0.0.1 [127.0.0.1] port 2022.
debug1: Connection established.
debug1: identity file /home/root/.ssh/id_rsa type -1
debug1: identity file /home/root/.ssh/id_rsa-cert type -1
debug1: identity file /home/root/.ssh/id_dsa type -1
debug1: identity file /home/root/.ssh/id_dsa-cert type -1
debug1: identity file /home/root/.ssh/id_ecdsa type -1
debug1: identity file /home/root/.ssh/id_ecdsa-cert type -1
debug1: identity file /home/root/.ssh/id_ecdsa_sk type -1
debug1: identity file /home/root/.ssh/id_ecdsa_sk-cert type -1
debug1: identity file /home/root/.ssh/id_ed25519 type -1
debug1: identity file /home/root/.ssh/id_ed25519-cert type -1
debug1: identity file /home/root/.ssh/id_ed25519_sk type -1
debug1: identity file /home/root/.ssh/id_ed25519_sk-cert type -1
debug1: identity file /home/root/.ssh/id_xmss type -1
debug1: identity file /home/root/.ssh/id_xmss-cert type -1
debug1: Local version string SSH-2.0-OpenSSH_8.2
debug1: Remote protocol version 2.0, remote software version
ConfD-7.3.1
debug1: match: ConfD-7.3.1 pat ConfD-* compat 0x00000001
debug2: fd 3 setting O_NONBLOCK
debug1: Authenticating to 127.0.0.1:2022 as 'root'
debug1: SSH2_MSG_KEXINIT sent
Connection closed by 127.0.0.1 port 2022

I am not able to understand why the connection is closed.

Regards,
Sukesh.R

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3168

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |djm at mindrot.org

--- Comment #6 from Damien Miller <djm at mindrot.org> ---
I recommend checking the server's log. A sshd run in debug mode ("sshd
-ddd") will give the most information.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3168

--- Comment #7 from Darren Tucker <dtucker at dtucker.net> ---
"Remote protocol version 2.0, remote software version ConfD-7.3.1"

The server is not OpenSSH, so you'll need to consult its documentation
for the equivalent debugging mode.

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3168

Darren Tucker <dtucker at dtucker.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |WORKSFORME

--- Comment #8 from Darren Tucker <dtucker at dtucker.net> ---
The original problem as reported has been resolved, the other mentioned
issue does not have sufficient information to debug (but one plausible
explanation is that the server is crashing on receipt of the KEX
packet, which is not a fault with OpenSSH.  You could try cutting down
KexAlgorithms, HostKeyAlgorithms, Ciphers, MACs to see if any of them
make a difference.)

Please open a new bug if you have any evidence of a fault with OpenSSH.

-- 
You are receiving this mail because:
You are watching someone on the CC list of the bug.
You are watching the assignee of the bug.

https://bugzilla.mindrot.org/show_bug.cgi?id=3168

Damien Miller <djm at mindrot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #9 from Damien Miller <djm at mindrot.org> ---
close bugs that were resolved in OpenSSH 8.5 release cycle

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.