-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Closed
Labels
3.2stablestable
Description
Version:
testssl.sh version 3.2rc3 from https://testssl.sh/dev/
(b5ad5bd 2024-12-06 15:03:47)
Using OpenSSL 1.0.2-bad [~179 ciphers]
on zwarte:./bin/openssl.Linux.x86_64
When running testssl against my local (=on same machine) webserver (cherrypy/cheroot, with self-signed certificate), testssl shows a bad grade (as expected), but the interesting part: dmesg shows segfaults in openssl.Linux.x86_64. It happens quite early in the testssl process
Test 2
When I run testssl against a lookalike webserver (cherrypy/cheroot, with self-signed certificate) on another machine on my LAN, the same dmesg errors occur on the machine running testssl (no messages on the remote machine).
So it's a thing on the machine running testssl?
Test 3
Ah, interesting: Based on #1934 (comment)
No demsg segfaults with `./testssl.sh --openssl=/usr/bin/openssl 127.0.0.1:8080
Using OpenSSL 3.0.13 30 Jan 2024 [~94 ciphers]
on zwarte:/usr/bin/openssl
`
So:
- is this OK / expected??
- is this a thing in the openssl provided by testssl?
Ubuntu 24.04, fully updated.
Looks a bit like #1275
[Sun Dec 29 21:36:02 2024] openssl.Linux.x[5546]: segfault at 2a060 ip 000000000002a060 sp 00007ffe5177c4c8 error 14 in openssl.Linux.x86_64[400000+3b9000] likely on CPU 0 (core 0, socket 0)
[Sun Dec 29 21:36:02 2024] Code: Unable to access opcode bytes at 0x2a036.
[Sun Dec 29 21:36:03 2024] openssl.Linux.x[5556]: segfault at 2a060 ip 000000000002a060 sp 00007fff3a82dbd8 error 14 in openssl.Linux.x86_64[400000+3b9000] likely on CPU 3 (core 1, socket 0)
[Sun Dec 29 21:36:03 2024] Code: Unable to access opcode bytes at 0x2a036.
[Sun Dec 29 21:36:04 2024] openssl.Linux.x[5564]: segfault at 2a060 ip 000000000002a060 sp 00007ffcb60cbbf8 error 14 in openssl.Linux.x86_64[400000+3b9000] likely on CPU 0 (core 0, socket 0)
[Sun Dec 29 21:36:04 2024] Code: Unable to access opcode bytes at 0x2a036.
[Sun Dec 29 21:36:05 2024] openssl.Linux.x[5573]: segfault at 2a060 ip 000000000002a060 sp 00007fff822d0588 error 14 in openssl.Linux.x86_64[400000+3b9000] likely on CPU 2 (core 0, socket 0)
[Sun Dec 29 21:36:05 2024] Code: Unable to access opcode bytes at 0x2a036.
[Sun Dec 29 21:36:07 2024] openssl.Linux.x[5581]: segfault at 2a060 ip 000000000002a060 sp 00007fff841846a8 error 14 in openssl.Linux.x86_64[400000+3b9000] likely on CPU 1 (core 1, socket 0)
[Sun Dec 29 21:36:07 2024] Code: Unable to access opcode bytes at 0x2a036.
[Sun Dec 29 21:36:08 2024] openssl.Linux.x[5591]: segfault at 2a060 ip 000000000002a060 sp 00007ffe67810128 error 14 in openssl.Linux.x86_64[400000+3b9000] likely on CPU 3 (core 1, socket 0)
[Sun Dec 29 21:36:08 2024] Code: Unable to access opcode bytes at 0x2a036.
[Sun Dec 29 21:36:09 2024] openssl.Linux.x[5614]: segfault at 2a060 ip 000000000002a060 sp 00007ffdfcaf9ad8 error 14 in openssl.Linux.x86_64[400000+3b9000] likely on CPU 3 (core 1, socket 0)
[Sun Dec 29 21:36:09 2024] Code: Unable to access opcode bytes at 0x2a036.
Metadata
Metadata
Assignees
Labels
3.2stablestable