FS#69311 - [testssl.sh] upstream error while scanning for vulnerabilities

Attached to Project: Community Packages
Opened by Alexandre ZANNI (noraj) - Wednesday, 13 January 2021, 15:14 GMT
Last edited by Toolybird (Toolybird) - Sunday, 07 May 2023, 05:01 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:


Additional info:
* package version: 3.0.2
* link to upstream bug report: https://github.com/drwetter/testssl.sh/issues/1823
* solution: upstream issue fixed in 3.0.4
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 07 May 2023, 05:01 GMT
Reason for closing:  Fixed
Additional comments about closing:  Stale. We're up to 3.0.8 now, so assuming fixed.
Comment by Jelle van der Waa (jelly) - Wednesday, 13 January 2021, 16:42 GMT
The tests fail or are unrunnable when updating to 3.0.4. If that's resolved we can update the package, would you mind helping us resolve it?
Comment by Alexandre ZANNI (noraj) - Wednesday, 13 January 2021, 18:36 GMT
Yeah the owner said 3.0.4 would fix it (see https://github.com/drwetter/testssl.sh/issues/1808#issuecomment-750905034). It was maybe fixed in 3.0.3 but it's said in the changelog to use 3.0.4 instead (see https://github.com/drwetter/testssl.sh/releases/tag/3.0.3).
I'm actually running the 3.0.4 check(), I have no error so far but it's very long to run so I'll keep you up to date if I encounter one. Have you any error report to share?
Comment by Alexandre ZANNI (noraj) - Wednesday, 13 January 2021, 18:59 GMT
I encountered this one but it doesn't seem related to testssl:

STARTTLS XMPP unit tests via OpenSSL --> jabber.org:5222 ...
not ok 8 -

# Failed test ''
# at t/25_baseline_starttls.t line 99.
# '
# Start 2021-01-13 19:54:02 -->> 208.68.163.218:5222 (jabber.org) <<--
#
# A record via: supplied IP "208.68.163.218"
# rDNS (208.68.163.218): xmpp.org.
# ./testssl.sh: line 18364: 252289 Segmentation fault (core dumped) $OPENSSL s_client $(s_client_options "$STARTTLS_OPTIMAL_PROTO $BUGS -connect "$NODEIP:$PORT" $PROXY -msg $STARTTLS $SNI") < /dev/null > $TMPFILE 2>> $ERRFILE
# ./testssl.sh: line 18364: 252300 Segmentation fault (core dumped) $OPENSSL s_client $(s_client_options "$STARTTLS_OPTIMAL_PROTO $BUGS -connect "$NODEIP:$PORT" $PROXY -msg $STARTTLS $SNI") < /dev/null > $TMPFILE 2>> $ERRFILE
# ./testssl.sh: line 18364: 252312 Segmentation fault (core dumped) $OPENSSL s_client $(s_client_options "$STARTTLS_OPTIMAL_PROTO $BUGS -connect "$NODEIP:$PORT" $PROXY -msg $STARTTLS $SNI") < /dev/null > $TMPFILE 2>> $ERRFILE
# ./testssl.sh: line 18364: 252323 Segmentation fault (core dumped) $OPENSSL s_client $(s_client_options "$STARTTLS_OPTIMAL_PROTO $BUGS -connect "$NODEIP:$PORT" $PROXY -msg $STARTTLS $SNI") < /dev/null > $TMPFILE 2>> $ERRFILE
# ./testssl.sh: line 18364: 252332 Segmentation fault (core dumped) $OPENSSL s_client $(s_client_options "$STARTTLS_OPTIMAL_PROTO $BUGS -connect "$NODEIP:$PORT" $PROXY -msg $STARTTLS $SNI") < /dev/null > $TMPFILE 2>> $ERRFILE
#
# jabber.org:5222 doesn't seem to be a TLS/SSL enabled server
# The results might look ok but they could be nonsense. Really proceed ? ("yes" to continue) -->
# '
# matches '(?^:(e|E)rror|(f|F)atal|\.\/testssl\.sh: line |Oops|s_client connect problem)'

Comment by Alexandre ZANNI (noraj) - Wednesday, 13 January 2021, 19:06 GMT
The unit tests may generate some false positives, I have a friend who used 3.0.4 from git repo on its Arch without issues. Are all the tests passing for the 3.0.2 right now?

I just `updpkgsums` the PKGBUILD to 3.0.4, installed it with `makepkg -fsri --nocheck` since there is only one test failing in check(), and re-ran the same command on the same target as in https://github.com/drwetter/testssl.sh/issues/1808#issuecomment-750905034 and now it works perfectly.

Loading...