From 0a8566302dd0c9cce65497611c1808c82328959f Mon Sep 17 00:00:00 2001 From: Krzysztof Opasiak Date: Mon, 6 May 2019 23:27:08 +0200 Subject: Don't wait forever for jdwp response Some of web services do not send any data when challenged with JDWP challenge. This makes the script waiting forever for response. To fix that let's introduce 10s timeout (experimental value) and replace empty string with a new line to avoid bash warnings. Issue-ID: SECCOM-231 Change-Id: I35546c001c5c54f298e8a4e346c2cf5d41e230ac Signed-off-by: Krzysztof Opasiak --- test/security/check_for_jdwp.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'test') diff --git a/test/security/check_for_jdwp.sh b/test/security/check_for_jdwp.sh index 7bcbade64..0facbff69 100755 --- a/test/security/check_for_jdwp.sh +++ b/test/security/check_for_jdwp.sh @@ -47,7 +47,8 @@ do_jdwp_handshake() { local jdwp_challenge="JDWP-Handshake\n" local jdwp_response="JDWP-Handshake" - local response=`nc $ip $port <<<$jdwp_challenge` + # 10s timeout to avoid hangs when service doesn't answer at all + local response=`nc -w 10 $ip $port <<<$jdwp_challenge | tr '\0' '\n'` if [[ $response == *"$jdwp_response"* ]]; then return 0 fi -- cgit 1.2.3-korg