Code Review / integration.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 743ad05) | patch
Don't treat error reply as a proper JDWP handshake 86/87486/1
authorKrzysztof Opasiak <k.opasiak@samsung.com>
Fri, 10 May 2019 20:43:10 +0000 (22:43 +0200)
committerKrzysztof Opasiak <k.opasiak@samsung.com>
Fri, 10 May 2019 20:50:16 +0000 (22:50 +0200)
commite095b67857f4bad35a366659d3d0f428f2747afb
tree412518f6261d28198422e85a91a91afb3568a3a1tree | snapshot
parent743ad0551bb67c8cf7b9d37effbf03c25444c8e2commit | diff
Don't treat error reply as a proper JDWP handshake

As it turned out thanks to Yan Yang some ONAP services tend to
return a propr JDWP handshake as a part of their error message.

Let's filter out those services by checking number of lines returned
by the server. We expect that proper JDWP handshake won't be longer
than a single line.

Issue-ID: SECCOM-231
Change-Id: I4b8950ebdf5fe118ec5f2dd5f4de583211784fb2
Signed-off-by: Krzysztof Opasiak <k.opasiak@samsung.com>
test/security/check_for_jdwp.sh diff | blob | history
Integration framework, automated tools, code and scripts, best practice guidance related to cross-project Continuous System Integration Testing (CSIT), and delivery of ONAP.