-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SegFault on Fedora 35 #319
Comments
gdb? strace? more info with verbose? |
Yes, check out https://www.rutschle.net/tech/sslh/doc/FAQ for how to report useful info.
Feb 25, 2022 17:49:48 Licaon_Kter ***@***.***>:
… gdb? strace? more info with verbose?
—
Reply to this email directly, view it on GitHub[#319 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ABGAU77DQX2HV75JI5ASUQDU46XJ7ANCNFSM5PKNYDPQ].
Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub].
You are receiving this because you are subscribed to this thread. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEgAAABICAYAAABV7bNHAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAArSURBVHic7cEBDQAAAMKg909tDjegAAAAAAAAAAAAAAAAAAAAAAAAAAA+DFFIAAEctgHwAAAAAElFTkSuQmCC###24x24:true###][Tracking image][https://github.com/notifications/beacon/ABGAU77S5NWDRS2D7FVDALTU46XJ7A5CNFSM5PKNYDP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOH2SUQGI.gif]
|
Thank you for the fast reply. Now I worked out the next command and here is the output:
Hope that helps. |
Ok so it explodes within libconfig. Whether it is sslh fault or libconfig fault is an open question (but traditionally it's sslh's fault).
Can you post your sslh config file and libconfig version? (And sslh version, just in case that's important)
Feb 25, 2022 21:22:08 Lasse Bruhn ***@***.***>:
… Thank you for the fast reply.
I already had a look there, but the command *file sslh-select* returned file not found, so I didn't continue.
Now I worked out the next command and here is the output:
*valgrind --leak-check=full sslh -v 2 -f
==475305== Memcheck, a memory error detector
==475305== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==475305== Using Valgrind-3.18.1 and LibVEX; rerun with -h for copyright info
==475305== Command: sslh -v 2 -f
==475305==
==475305== Invalid read of size 2
==475305== at 0x486B9C4: config_setting_is_aggregate (libconfig.c:1772)
==475305== by 0x486C5EC: config_setting_length (libconfig.c:1591)
==475305== by 0x406173: cfg_as_string (sslh-conf.c:1684)
==475305== by 0x406A3C: sslhcfg_cl_parse (sslh-conf.c:1794)
==475305== by 0x409CB9: main (sslh-main.c:211)
==475305== Address 0x8 is not stack'd, malloc'd or (recently) free'd
==475305==
==475305==
==475305== Process terminating with default action of signal 11 (SIGSEGV): dumping core
==475305== Access not within mapped region at address 0x8
==475305== at 0x486B9C4: config_setting_is_aggregate (libconfig.c:1772)
==475305== by 0x486C5EC: config_setting_length (libconfig.c:1591)
==475305== by 0x406173: cfg_as_string (sslh-conf.c:1684)
==475305== by 0x406A3C: sslhcfg_cl_parse (sslh-conf.c:1794)
==475305== by 0x409CB9: main (sslh-main.c:211)
==475305== If you believe this happened as a result of a stack
==475305== overflow in your program's main thread (unlikely but
==475305== possible), you can try to increase the size of the
==475305== main thread stack using the --main-stacksize= flag.
==475305== The main thread stack size used in this run was 8388608.
==475305==
==475305== HEAP SUMMARY:
==475305== in use at exit: 3,869 bytes in 28 blocks
==475305== total heap usage: 33 allocs, 5 frees, 6,393 bytes allocated
==475305==
==475305== LEAK SUMMARY:
==475305== definitely lost: 0 bytes in 0 blocks
==475305== indirectly lost: 0 bytes in 0 blocks
==475305== possibly lost: 0 bytes in 0 blocks
==475305== still reachable: 3,869 bytes in 28 blocks
==475305== suppressed: 0 bytes in 0 blocks
==475305== Reachable blocks (those to which a pointer was found) are not shown.
==475305== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==475305==
==475305== For lists of detected and suppressed errors, rerun with: -s
==475305== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Speicherzugriffsfehler (Speicherabzug geschrieben)
*
Hope that helps.
—
Reply to this email directly, view it on GitHub[#319 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ABGAU76MIVFQF65D42AB54TU47QGHANCNFSM5PKNYDPQ].
Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub].
You are receiving this because you commented. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAEgAAABICAYAAABV7bNHAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAArSURBVHic7cEBDQAAAMKg909tDjegAAAAAAAAAAAAAAAAAAAAAAAAAAA+DFFIAAEctgHwAAAAAElFTkSuQmCC###24x24:true###][Tracking image][https://github.com/notifications/beacon/ABGAU74DLL3RLMZ64NAS7Y3U47QGHA5CNFSM5PKNYDP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOH2UFXYI.gif]
|
My
I've sslh version 1.21c and libconfig version 1.7.3. |
Hi all, I have the same problem here with F35. Default config.
|
I just remembered that other old issue: #30 maybe quote the integer parameters for verbose, timeout and log_level? |
I tried it but same error.
|
you still have |
|
Thanks for pointing out the quoted integers. I changed my config accordingly:
I hope, I didn't overlook something, but unfortunately it doesn't work for me, but still crashes:
Looks like the error output hasn't changed. I also wonder, why it solved the problem for @k-nard but not for me!? |
Maybe it would also be an option for me to run sslh via Docker. But I need sslh to split the traffic according to its SNI. Is that possible with Docker? I couldn't find any Docker config option for that in the docs. |
My bad, I tried again when I saw your message. It does not work. I probably test on a F34 yesterday. Sorry.
|
The same problem on FC36
|
Hello everyone! A line with a problem is: |
ah. So FWIW this was fixed in sslh two years ago in 24e7f46, following a libconfig evolution (hyperrealm/libconfig#196). |
I assume the answers are satisfactory. |
Expected behavior:
Actual behavior:
Steps to reproduce:
Would be very happy to get this tool running again on the latest Fedora release.
The text was updated successfully, but these errors were encountered: