Bug 2215951

Summary: Segmentation fault on running sslh
Product: [Fedora] Fedora Reporter: Hormiga <fedora>
Component: sslhAssignee: Alex Perez <aperez>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 38CC: aperez, mmalik
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-22 14:08:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hormiga 2023-06-19 13:13:38 UTC 
Description of problem:
Running of sslh causes segmentation fault because of incompatibility with libconfig.

Version-Release number of selected component (if applicable): 1.21c

How reproducible: Every time

Steps to Reproduce:
1. Install: dnf install sslh
2. Run without config: sslh -f

Actual results:
"Segmentation fault (core dumped)"

Expected results:
"At least one target protocol must be specified."

Additional info:
According to github issue (https://github.com/yrutschle/sslh/issues/319), package has this problem since Fedora 35.
Latest messages shows that the problem is in incompatibility of this version of sslh with current libconfig - this was fixed in sslh version 1.22.
Comment 1 Milos Malik 2023-06-29 13:15:45 UTC 
I believe I encountered the same issue:

# coredumpctl info -1
           PID: 21565 (sslh)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Thu 2023-06-29 09:14:02 EDT (19s ago)
  Command Line: /usr/sbin/sslh -F/etc/sslh.cfg
    Executable: /usr/sbin/sslh
 Control Group: /system.slice/sslh.service
          Unit: sslh.service
         Slice: system.slice
       Boot ID: e94467f7e87846e9be3ae37f41572df9
    Machine ID: 4bf80b5319374414937ecae37aaa5c42
      Hostname: vm-10-0-185-58.hosted.upshift.rdu2.redhat.com
       Storage: /var/lib/systemd/coredump/core.sslh.0.e94467f7e87846e9be3ae37f4>
  Size on Disk: 56.1K
       Package: sslh/1.21c-6.fc38
      build-id: 55b4375f449bbefa24d0e52e1c3ed765da673003
       Message: Process 21565 (sslh) of user 0 dumped core.
                
                Module liblz4.so.1 from rpm lz4-1.9.4-3.fc39.x86_64
                Module libzstd.so.1 from rpm zstd-1.5.5-1.fc39.x86_64
                Module liblzma.so.5 from rpm xz-5.4.3-1.fc39.x86_64
                Module libpcre.so.1 from rpm pcre-8.45-1.fc38.3.x86_64
                Module libsystemd.so.0 from rpm systemd-253.5-6.fc39.x86_64
                Module libcap.so.2 from rpm libcap-2.48-6.fc38.x86_64
                Module libpcreposix.so.0 from rpm pcre-8.45-1.fc38.3.x86_64
                Module sslh from rpm sslh-1.21c-6.fc38.x86_64
                Stack trace of thread 21565:
                #0  0x00007fa0c7327a04 config_setting_is_aggregate (libconfig.s>
                #1  0x00007fa0c7328585 config_setting_length (libconfig.so.11 +>
                #2  0x000055c820d89e2f cfg_as_string (sslh + 0x6e2f)
                #3  0x000055c820d8fd47 sslhcfg_cl_parse.constprop.0 (sslh + 0xc>
                #4  0x000055c820d87d96 main (sslh + 0x4d96)
                #5  0x00007fa0c6e280ca __libc_start_call_main (libc.so.6 + 0x28>
                #6  0x00007fa0c6e2818b __libc_start_main@@GLIBC_2.34 (libc.so.6>
                #7  0x000055c820d89665 _start (sslh + 0x6665)
                ELF object binary architecture: AMD x86-64
#
Comment 2 Aoife Moloney 2024-05-22 14:08:54 UTC 
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.