bsi-bund / task Goto Github PK

The "TaSK Framework" is a configurable test tool for performing TLS conformity tests based on the Technical Guideline TR-03116-TS.

Java 78.74% Shell 1.45% Python 0.06% XSLT 1.23% CMake 0.46% C++ 18.01% Dockerfile 0.05% Batchfile 0.01%

task's Introduction

TaSK Framework

Version 1.0.1

The "TaSK Framework" is a configurable test tool for performing TLS conformity tests based on the Technical Guideline TR-03116-TS. The test tool has a modular structure to enable efficient further development and applicability in different test scenarios. This testing tool enables test centers to efficiently and effectively test various DUTs from different application-specific scenarios for conformity. Furthermore, it offers manufacturers the possibility to perform independent tests during development. In the case of TLS implementations, the test tool itself checks both the manufacturer's specifications and direct conformity with the BSI's technical guidelines.

Structure

The framework consists of two components: "TaSK" and "TLS Test Tool".

TaSK

The test case runner with report generator and validation mechanism for the input documents. It is started via a command line interface and can be executed locally or via a REST API. The configuration is done via XML files. The component, including in-depth documentation, is provided in task.

TLS Test Tool

The TLS test tool is a stand-alone application that is capable of performing different TLS handshakes and apply manipulations on the TLS communication. It is used in the background by TaSK. Depending on the type of the DUT and the test-scenario, it can act as a TLS client or a TLS server. The component, including in-depth documentation, is provided in tlstesttool.

License

The TaSK framework is licensed under the European Union Public Licence Version 1.2 (or-later). For more information on the license, see the included license text itself or the according website of the European Commission.

task's People

Contributors

Stargazers

Watchers

Forkers

vschwaberow bufkin p-w xoryouyou laukr adesso-as-a-service elschnagoo duncan-howe

task's Issues

Compiling failed on MacOS

[ 97%] Building C object CMakeFiles/minigzip.dir/test/minigzip.o
/Users/volker/src/TaSK/tlstesttool/build/EP_ZLIB-prefix/src/EP_ZLIB/test/minigzip.c:351:6: warning: a function definition without a prototype is deprecated in all versions of C and is not supported in C2x [-Wdeprecated-non-prototype]
void error(msg)
^
/Users/volker/src/TaSK/tlstesttool/build/EP_ZLIB-prefix/src/EP_ZLIB/test/minigzip.c:362:6: warning: a function definition without a prototype is deprecated in all versions of C and is not supported in C2x [-Wdeprecated-non-prototype]
void gz_compress(in, out)
^
/Users/volker/src/TaSK/tlstesttool/build/EP_ZLIB-prefix/src/EP_ZLIB/test/minigzip.c:430:6: warning: a function definition without a prototype is deprecated in all versions of C and is not supported in C2x [-Wdeprecated-non-prototype]
void gz_uncompress(in, out)
^
/Users/volker/src/TaSK/tlstesttool/build/EP_ZLIB-prefix/src/EP_ZLIB/test/minigzip.c:457:6: warning: a function definition without a prototype is deprecated in all versions of C and is not supported in C2x [-Wdeprecated-non-prototype]
void file_compress(file, mode)
^
/Users/volker/src/TaSK/tlstesttool/build/EP_ZLIB-prefix/src/EP_ZLIB/test/minigzip.c:496:6: warning: a function definition without a prototype is deprecated in all versions of C and is not supported in C2x [-Wdeprecated-non-prototype]
void file_uncompress(file)
^
/Users/volker/src/TaSK/tlstesttool/build/EP_ZLIB-prefix/src/EP_ZLIB/test/minigzip.c:556:5: warning: a function definition without a prototype is deprecated in all versions of C and is not supported in C2x [-Wdeprecated-non-prototype]
int main(argc, argv)
^
/Users/volker/src/TaSK/tlstesttool/build/EP_ZLIB-prefix/src/EP_ZLIB/test/minigzip.c:556:5: warning: a function definition without a prototype is deprecated in all versions of C and is not supported in C2x [-Wdeprecated-non-prototype]
7 warnings generated.
[100%] Linking C executable minigzip
[100%] Built target minigzip
[ 37%] Performing install step for 'EP_ZLIB'
[ 44%] Built target zlib
[ 88%] Built target zlibstatic
[ 94%] Built target example
[100%] Built target minigzip
Install the project...
-- Install configuration: ""
-- Installing: /Users/volker/src/TaSK/tlstesttool/build/EP_BASE/lib/libz.a
-- Installing: /Users/volker/src/TaSK/tlstesttool/build/EP_BASE/include/zconf.h
-- Installing: /Users/volker/src/TaSK/tlstesttool/build/EP_BASE/include/zlib.h
-- Installing: /Users/volker/src/TaSK/tlstesttool/build/EP_BASE/share/man/man3/zlib.3
-- Installing: /Users/volker/src/TaSK/tlstesttool/build/EP_BASE/share/pkgconfig/zlib.pc
[ 40%] Completed 'EP_ZLIB'
[ 40%] Built target EP_ZLIB
[ 42%] Creating directories for 'EP_MBEDTLS'
[ 45%] Performing download step (download, verify and extract) for 'EP_MBEDTLS'
-- Downloading...
dst='/Users/volker/src/TaSK/tlstesttool/build/EP_MBEDTLS-prefix/src/mbedtls-2.2.1.tar.gz'
timeout='none'
inactivity timeout='none'
-- Using src='https://github.com/Mbed-TLS/mbedtls/archive/refs/tags/mbedtls-2.2.1.tar.gz'
-- verifying file...
file='/Users/volker/src/TaSK/tlstesttool/build/EP_MBEDTLS-prefix/src/mbedtls-2.2.1.tar.gz'
-- Downloading... done
-- extracting...
src='/Users/volker/src/TaSK/tlstesttool/build/EP_MBEDTLS-prefix/src/mbedtls-2.2.1.tar.gz'
dst='/Users/volker/src/TaSK/tlstesttool/build/EP_MBEDTLS-prefix/src/EP_MBEDTLS'
-- extracting... [tar xfz]
-- extracting... [analysis]
-- extracting... [rename]
-- extracting... [clean up]
-- extracting... done
[ 47%] No update step for 'EP_MBEDTLS'
[ 50%] Performing patch step for 'EP_MBEDTLS'
patching file 'include/mbedtls/config.h'
patching file 'include/mbedtls/ssl.h'
patching file 'library/ssl_cli.c'
patching file 'include/mbedtls/ssl.h'
patching file 'library/ssl_cli.c'
patching file 'library/debug.c'
patching file 'library/ssl_cli.c'
patching file 'library/ssl_cli.c'
patching file 'include/mbedtls/ssl.h'
1 out of 1 hunks failed--saving rejects to 'include/mbedtls/ssl.h.rej'
patching file 'library/ssl_cli.c'
patching file 'library/ssl_srv.c'
patching file 'library/ssl_tls.c'
make[2]: *** [EP_MBEDTLS-prefix/src/EP_MBEDTLS-stamp/EP_MBEDTLS-patch] Error 1
make[1]: *** [CMakeFiles/EP_MBEDTLS.dir/all] Error 2
make: *** [all] Error 2

OS: MacOS 13.0 Ventura
clang --version
Homebrew clang version 15.0.6
Target: x86_64-apple-darwin22.1.0
Thread model: posix
InstalledDir: /usr/local/opt/llvm/bin

Provide Image on Docker Hub

You already provide a Dockerfile.
Why don't you push images to Docker Hub?

Doku of TLS Test Tool

on Debain it's been build with

./tlstesttool/build/EP_BASE/bin/openssl version
OpenSSL 3.0.1 14 Dec 2021 (Library: OpenSSL 3.0.1 14 Dec 2021)

./tlstesttool/build/EP_BASE/bin/openssl ciphers -v
TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD
TLS_CHACHA20_POLY1305_SHA256 TLSv1.3 Kx=any Au=any Enc=CHACHA20/POLY1305(256) Mac=AEAD
TLS_AES_128_GCM_SHA256 TLSv1.3 Kx=any Au=any Enc=AESGCM(128) Mac=AEAD

but I cant find the config paramter in section "2.2.5 TLS options" of the doku
I guess it might be (3,4) - would be nice if added

Different understandings of server behavior when the client hello carries compression algorithm

Issue Type: Tool Implementation Principle

Testcase name: Compression not selected

Testcase number: TLS_B1_FR_12

Test code: TLS_B1_FR_12.java

Description:
The RFC of TLS 1.2 does not require the behavior (disconnection or ignoring) of handling the client Hello carrying compression algorithm.

However, the tool only allows that server hello packet does not carry compression algorithm after receiving the client hello packet carrying compression algorithm.

We thint if the tested device returns an alert packet and disconnects the TLS connection after receiving the client Hello packet with the compression algorithm, it indicates that the tested device does not select the compression algorithm and meets the requirement. In this case, we think the test case should be PASS.

Looking forward to further discussion.

shadow variable

/tlstesttool/src/tls/mbedtls/TlsSession.cpp line 275
code:
const auto result = mbedtls_ssl_fetch_input(&ssl, 5);
const bool msgHeaderIndicatesAlert = (0 == result) && (MBEDTLS_SSL_MSG_ALERT == ssl.in_hdr[0]);
if (msgHeaderIndicatesAlert || forceRead) {
const auto result = mbedtls_ssl_read_record(&ssl); // <- shadow variable

Building on Apple Silicon

When building with Docker on MacBook Pro with M1 Pro, the build fails with gcc: error: unrecognized command-line option '-m64'.

Command to build

docker build -t bsi-task:latest

Error

...
#0 13.99 make depend && make _build_sw
#0 13.99 make[1]: Entering directory '/task/src/tlstesttool/build/EP_OPENSSL-prefix/src/EP_OPENSSL'
#0 13.99 make[1]: Leaving directory '/task/src/tlstesttool/build/EP_OPENSSL-prefix/src/EP_OPENSSL'
#0 13.99 make[1]: Entering directory '/task/src/tlstesttool/build/EP_OPENSSL-prefix/src/EP_OPENSSL'
#0 13.99 gcc  -I. -Iinclude -Iapps/include  -fPIC -pthread -m64 -Wa,--noexecstack -Wall -O3 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSLDIR="\"/task/src/tlstesttool/build/EP_BASE/ssl\"" -DENGINESDIR="\"/task/src/tlstesttool/build/EP_BASE/lib64/engines-3\"" -DMODULESDIR="\"/task/src/tlstesttool/build/EP_BASE/lib64/ossl-modules\"" -DOPENSSL_BUILDING_OPENSSL -DNDEBUG  -MMD -MF apps/lib/libapps-lib-app_libctx.d.tmp -MT apps/lib/libapps-lib-app_libctx.o -c -o apps/lib/libapps-lib-app_libctx.o apps/lib/app_libctx.c
#0 13.99 gcc: error: unrecognized command-line option '-m64'
#0 13.99 make[1]: *** [Makefile:3506: apps/lib/libapps-lib-app_libctx.o] Error 1
#0 13.99 make[1]: Leaving directory '/task/src/tlstesttool/build/EP_OPENSSL-prefix/src/EP_OPENSSL'
#0 13.99 make: *** [Makefile:2516: build_sw] Error 2
#0 13.99 ninja: build stopped: subcommand failed.
------
Dockerfile:29
--------------------
  27 |     WORKDIR /task/src/tlstesttool/build
  28 |     # prepare build and run it parallel with ninja
  29 | >>> RUN cmake -G Ninja -DCMAKE_BUILD_TYPE=Release .. && ninja
  30 |     
  31 |     # switch to task
--------------------
ERROR: failed to solve: process "/bin/sh -c cmake -G Ninja -DCMAKE_BUILD_TYPE=Release .. && ninja" did not complete successfully: exit code: 1

Workaround

In the FROM line, set the Arch to amd64.
This slows down the build process extremely (16,5 hours on my MacBook Pro with M1 Pro).

Update: docker-compose.yml also needs an update.

diff --git a/Dockerfile b/Dockerfile
index 33c023b..b857a7a 100755
--- a/Dockerfile
+++ b/Dockerfile
@@ -2,7 +2,7 @@
 # - edit /var/snap/docker/current/config/daemon.json and replace “overlay2” with “vfs” for the storage-driver
 # - run sudo snap restart docker
 
-FROM ubuntu:22.04
+FROM --platform=linux/amd64 ubuntu:22.04
 
 # install dependencies
 RUN apt-get update
diff --git a/docker-compose.yml b/docker-compose.yml
index c405ce0..671a547 100755
--- a/docker-compose.yml
+++ b/docker-compose.yml
@@ -2,6 +2,7 @@ version: '3'
 services:
   task:
     image: task-docker
+    platform: linux/amd64
     container_name: task-docker
     build:
       context: .

Suggested fix

It would be cool, if you could make the gcc work on Apple Silicon.

TLS check for SMTP?

Hello,

is there any way to get the TLS test tool running with STARTTLS?
I tried some things while running TaSK itself and "StartConnectionArguments" allowed me to trigger OpenSSL with "-starttls smtp" but this will not be used for the TLS tests by the TLS tool. The configurations files has no possibility to enable STARTTLS.

Or is this just a missing feature?

Greetings,
Jan

update your vulnerable Library: OpenSSL 3.0.2 15 Mar 2022 in Docker to an accurate actual version

Could you please provide a Dockerfile?

Could you please provide a Dockerfile? This would ease the usage of TaSK.

When building the tlstesttool an old and vulnerable openssl 3.0.1 is included

[ 62%] Creating directories for 'EP_OPENSSL'
[ 65%] Performing download step (download, verify and extract) for 'EP_OPENSSL'
-- Downloading...
   dst='/home/user/gits/TaSK/tlstesttool/build/EP_OPENSSL-prefix/src/openssl-3.0.1.tar.gz'
   timeout='none'
   inactivity timeout='none'
-- Using src='https://www.openssl.org/source/openssl-3.0.1.tar.gz'
                                                     ^^^^^

compilation fails on Ubuntu 22.10

Log:

../../apache-maven-3.8.7/bin/mvn clean install -e
...
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for com.achelos.task 0.4.2:
[INFO] 
[INFO] com.achelos.task ................................... SUCCESS [  9.339 s]
[INFO] com.achelos.task.utilities ......................... FAILURE [  1.308 s]
[INFO] com.achelos.task.logging ........................... SKIPPED
[INFO] com.achelos.task.commons ........................... SKIPPED
[INFO] com.achelos.task.xmlparser ......................... SKIPPED
[INFO] com.achelos.task.configuration ..................... SKIPPED
[INFO] com.achelos.task.testsuitesetup .................... SKIPPED
[INFO] com.achelos.task.abstracttestsuite ................. SKIPPED
[INFO] com.achelos.task.micsverifier ...................... SKIPPED
[INFO] com.achelos.task.commandlineexecution .............. SKIPPED
[INFO] com.achelos.task.tr03116ts ......................... SKIPPED
[INFO] com.achelos.task.testcaseexecutionengine ........... SKIPPED
[INFO] com.achelos.task.abstractinterface ................. SKIPPED
[INFO] com.achelos.task.reporting ......................... SKIPPED
[INFO] com.achelos.task.rest-impl ......................... SKIPPED
[INFO] com.achelos.task.commandlineinterface .............. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  10.777 s
[INFO] Finished at: 2023-01-12T15:49:34+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project com.achelos.task.utilities: Fatal error compiling: error: invalid target release: 17 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project com.achelos.task.utilities: Fatal error compiling
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:375)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:298)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke [INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  10.751 s
[INFO] Finished at: 2023-01-12T15:46:15+01:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project com.achelos.task.utilities: Fatal error compiling: error: invalid target release: 17 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) on project com.achelos.task.utilities: Fatal error compiling
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavrenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1140)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:188)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifemvn clean install -e
cycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.codehaus.plexus.compiler.CompilerException: error: invalid target release: 17
    at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess (JavaxToolsCompiler.java:173)
    at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile (JavacCompiler.java:174)
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1129)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:188)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: java.lang.IllegalArgumentException: error: invalid target release: 17
    at com.sun.tools.javac.main.Arguments.errorr (Arguments.java:907)
    at com.sun.tools.javac.main.Arguments.doProcessArgs (Arguments.java:383)
    at com.sun.tools.javac.main.Arguments.processArgs (Arguments.java:347)
    at com.sun.tools.javac.main.Arguments.init (Arguments.java:246)
    at com.sun.tools.javac.api.JavacTool.getTask (JavacTool.java:185)
    at com.sun.tools.javac.api.JavacTool.getTask (JavacTool.java:119)
    at com.sun.tools.javac.api.JavacTool.getTask (JavacTool.java:68)
    at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess (JavaxToolsCompiler.java:125)
    at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile (JavacCompiler.java:174)
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1129)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:188)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:210)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:156)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:148)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :com.achelos.task.utilities(NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error compiling
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1140)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:188)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:298)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: org.codehaus.plexus.compiler.CompilerException: error: invalid target release: 17
    at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess (JavaxToolsCompiler.java:173)
    at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile (JavacCompiler.java:174)
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1129)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:188)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:298)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
Caused by: java.lang.IllegalArgumentException: error: invalid target release: 17
    at com.sun.tools.javac.main.Arguments.error (Arguments.java:907)
    at com.sun.tools.javac.main.Arguments.doProcessArgs (Arguments.java:383)
    at com.sun.tools.javac.main.Arguments.processArgs (Arguments.java:347)
    at com.sun.tools.javac.main.Arguments.init (Arguments.java:246)
    at com.sun.tools.javac.api.JavacTool.getTask (JavacTool.java:185)
    at com.sun.tools.javac.api.JavacTool.getTask (JavacTool.java:119)
    at com.sun.tools.javac.api.JavacTool.getTask (JavacTool.java:68)
    at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess (JavaxToolsCompiler.java:125)
    at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile (JavacCompiler.java:174)
    at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute (AbstractCompilerMojo.java:1129)
    at org.apache.maven.plugin.compiler.CompilerMojo.execute (CompilerMojo.java:188)
    at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo (DefaultBuildPluginManager.java:137)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute2 (MojoExecutor.java:370)
    at org.apache.maven.lifecycle.internal.MojoExecutor.doExecute (MojoExecutor.java:351)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:215)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:171)
    at org.apache.maven.lifecycle.internal.MojoExecutor.execute (MojoExecutor.java:163)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:117)
    at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject (LifecycleModuleBuilder.java:81)
    at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build (SingleThreadedBuilder.java:56)
    at org.apache.maven.lifecycle.internal.LifecycleStarter.execute (LifecycleStarter.java:128)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:298)
    at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
    at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
    at org.apache.maven.cli.MavenCli.execute (MavenCli.java:960)
    at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:293)
    at org.apache.maven.cli.MavenCli.main (MavenCli.java:196)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
    at jdk.internal.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.java:62)
    at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke (Method.java:566)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced (Launcher.java:282)
    at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:225)
    at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:406)
    at org.codehaus.plexus.classworlds.launcher.Launcher.main (Launcher.java:347)
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :com.achelos.task.utilities

Build fails behind Proxy Server

If behind a proxy server (which is often the case in a corporate environment) installation fails, because it cannot connect to test-check.de (or did I do something wrong?)

2023-01-13T10:14:25.019 INFO MSG: MICS Verifier: Successfully parsed the MICS file: ../data/input/ExampleMICS_Server.xml
2023-01-13T10:14:25.019 INFO MSG: MICS Verifier: Verifying the MICS file..
2023-01-13T10:14:25.019 DEBUG MSG: MICS Verifier: Checking if "CHECK_CERTS" profile is set in the MICS file.
2023-01-13T10:14:25.019 DEBUG MSG: MICS Verifier: Found "CHECK_CERTS" profile in the MICS file.
2023-01-13T10:14:25.019 DEBUG MSG: MICS Verifier: Verifying the existence of provided certificate files.
2023-01-13T10:14:25.019 DEBUG MSG: MICS Verifier: Existence of provided certificate files successfully verified.
2023-01-13T10:14:25.019 DEBUG MSG: MICS Verifier: Searching for applicable application specification and application mapping.
2023-01-13T10:14:25.019 DEBUG MSG: MICS Verifier: Found applicable application specification.
2023-01-13T10:14:25.019 DEBUG MSG: MICS Verifier: Found applicable application mapping.
2023-01-13T10:14:25.019 INFO MSG: MICS Verifier: Verifying the Device Under Test.
2023-01-13T10:14:25.021 DEBUG MSG: MICS Verifier: Running DUT verifier on the provided MICS file.
2023-01-13T10:14:25.021 DEBUG MSG: MICS Verifier: DUT is of type: TR-03116-4-SERVER
2023-01-13T10:14:25.021 DEBUG MSG: MICS Verifier: Verifying server URL: tls-check.de.
java.lang.RuntimeException: MICS Verifier: Error occurred while trying to verify the provided MICS file.
at com.achelos.task.micsverifier.MICSVerifier.verifyMICS(MICSVerifier.java:182)
at com.achelos.task.micsverifier.MICSVerifier.verifyMICS(MICSVerifier.java:96)
at micsverifier.TestMICSVerifier.testMICSVerifier(TestMICSVerifier.java:40)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at org.junit.platform.commons.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:628)
at org.junit.jupiter.engine.execution.ExecutableInvoker.invoke(ExecutableInvoker.java:117)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.lambda$invokeTestMethod$7(TestMethodTestDescriptor.java:184)
at org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.invokeTestMethod(TestMethodTestDescriptor.java:180)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:127)
at org.junit.jupiter.engine.descriptor.TestMethodTestDescriptor.execute(TestMethodTestDescriptor.java:68)
at org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$5(NodeTestTask.java:135)
2023-01-13T10:14:25.023 ERROR MSG: MICS Verifier: DUT has a server type, but the provided server URL could not be verified. EXC:java.net.UnknownHostException: tls-check.de: Temporary failure in name resolution

Signature_algorithms extension configuration and parsing logic are inconsistent

Issue Type: Tool Configuration

Testcase name: signature_algorithms extension

Testcase number: TLS_B1_GP_03_T

Test code: TLS_B1_GP_03_T.java

Description:
In TestRunPlan mode and TLS 1.2 tested, only reserverd_4 can be configured in the XML file to configure algorithm as rsa_pss_rsae_sha256. Otherwise, the tool cannot send expected packets carrying rsa_pss_rsae_sha256 algorithm.

However, when parsing the received packets, the parsed result is rsa_pss_rsae_sha256 (as expected), which is different from reserverd_4 configured in the XML file. As a result, the test case is failed.

Question for the purpose of testcase TLS_B1_GP_09

Issue Type: Redundant test items

Testcase name: Select strongest cipher suite

Testcase number: TLS_B1_GP_09

Test code: TLS_B1_GP_09.java

Description:
The TLS server selects the cipher suites based on the client preference. We think that this testcase is not necessary when the tested device functions as the TLS server.

In addition, what is the basis for sorting cipher suites? Is it based on industry specifications or RFC requirements? Looking forward to further discussion.

Only supporting non-ECC ciphersuite instead of traversing all security ciphersuites.

Issue Type: Tool Implementation Principle

Testcase name: Supported TLS versions

Testcase number: TLS_B1_GP_01_T

Test code: TLS_B1_GP_01_T.java

Description:
The test tool requires that the non-ECC cipher suite be used. Otherwise, the TLS handshake fails and the test fails. We believe that the test tool should use or traverse more secure cipher suites by default to complete the TLS handshake and verify the TLS version supported by the device.

The requirement of signature_algorithms in TLS 1.3 inconsistent with RFC 8446

Issue Type: Test Principles

Testcase name: signature_algorithms extension

Testcase number: TLS_B1_GP_03_T

Test code: TLS_B1_GP_03_T.java

Description:
The test tool only allows that the algorithm in "signature_algorithms extension" is consistent with the public key algorithm in certificate, which complies with RFC5246 (TLS 1.2).

But the TLS 1.3 (RFC 8446) does not make such a requirement refer to 4.4.2.2.

   If the server cannot produce a certificate chain that is signed only
   via the indicated supported algorithms, then it SHOULD continue the
   handshake by sending the client a certificate chain of its choice
   that may include algorithms that are not known to be supported by the
   client.  This fallback chain SHOULD NOT use the deprecated SHA-1 hash
   algorithm in general, but MAY do so if the client's advertisement
   permits it, and MUST NOT do so otherwise.

I don't know if my understanding is correct, hope to get your reply.

License file missing

The README references an "included license text" for the TaSK framework:

TaSK/README.md

Lines 23 to 25 in d3b7dd5

 ## License 

 The TaSK framework is licensed under the EUPL-1.2-or-later. 

 For more information on the license, see the included license text itself, or the according [website](https://joinup.ec.europa.eu/collection/eupl/eupl-text-eupl-12) of the European Commission.

However, the license is only included for the TLS Test Tool.

Compiling failed! mbedTLS!

Hi,

I tried to compile the tlstesttool as described in the README, but got the following error:

/home/Documents/TaSK/tlstesttool/src/tls/mbedtls/TlsSession.cpp: In function ‘std::string TlsTestTool::MbedTls::errorToString(int)’: /home/Documents/TaSK/tlstesttool/src/tls/mbedtls/TlsSession.cpp:144:25: error: ‘str’ may be used uninitialized [-Werror=maybe-uninitialized] 144 | mbedtls_strerror(errorCode, str.data(), str.size()); | ~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In file included from /home/Documents/TaSK/tlstesttool/src/tls/mbedtls/../../tls/TlsNumbers.h:21, from /home/Documents/TaSK/tlstesttool/src/tls/mbedtls/../../tls/TlsHashAlgorithm.h:21, from /home/Documents/TaSK/tlstesttool/src/tls/mbedtls/../../tls/TlsSession.h:25, from /home/Documents/TaSK/tlstesttool/src/tls/mbedtls/TlsSession.h:21, from /home/Documents/TaSK/tlstesttool/src/tls/mbedtls/TlsSession.cpp:18: /usr/include/c++/11/array:176:7: note: by argument 1 of type ‘const std::array<char, 1024>*’ to ‘constexpr std::array<_Tp, _Nm>::size_type std::array<_Tp, _Nm>::size() const [with _Tp = char; long unsigned int _Nm = 1024]’ declared here 176 | size() const noexcept { return _Nm; } | ^~~~ /home/Documents/TaSK/tlstesttool/src/tls/mbedtls/TlsSession.cpp:143:32: note: ‘str’ declared here 143 | std::array<char, 1024> str; | ^~~ cc1plus: all warnings being treated as errors gmake[2]: *** [src/tls/mbedtls/CMakeFiles/TlsTestToolTlsMbedTls.dir/build.make:90: src/tls/mbedtls/CMakeFiles/TlsTestToolTlsMbedTls.dir/TlsSession.cpp.o] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:427: src/tls/mbedtls/CMakeFiles/TlsTestToolTlsMbedTls.dir/all] Error 2 gmake: *** [Makefile:91: all] Error 2

OS:
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy

offer in the dockerfile automatic security fixes for OS and Java

Building failed! Patching of EP_MBEDTLS

patching file 'include/mbedtls/config.h'
patching file 'include/mbedtls/ssl.h'
patching file 'library/ssl_cli.c'
patching file 'include/mbedtls/ssl.h'
patching file 'library/ssl_cli.c'
patching file 'library/debug.c'
patching file 'library/ssl_cli.c'
patching file 'library/ssl_cli.c'
patching file 'include/mbedtls/ssl.h'
1 out of 1 hunks failed--saving rejects to 'include/mbedtls/ssl.h.rej'
patching file 'library/ssl_cli.c'
patching file 'library/ssl_srv.c'
patching file 'library/ssl_tls.c'
make[2]: *** [EP_MBEDTLS-prefix/src/EP_MBEDTLS-stamp/EP_MBEDTLS-patch] Error 1
make[1]: *** [CMakeFiles/EP_MBEDTLS.dir/all] Error 2
make: *** [all] Error 2

OS: macOS 13.2.1
cmake 3.25.3

Execute a TestRunPlan over ReST requires dummy RMIURL.

I want to upload and execute my working TestRunPlan over ReST endpoint {baseUrl}/execute/trp and get the error.

    "statuscode": "400",
    "errormessage": "Bad Request: Received TestRunplan could not be parsed: TaSKRequestHandler: RMI URL is not defined in TestRunPlan.",

I'm a little bit confused why I must to add a (dummy) RMI endpoint to my TestRunPlan. From my point of view it is only necessary for Clients under test. I'm able to continue with this workaround.

    <RMIURL>localhost</RMIURL>
    <RMIPort>1099</RMIPort>

no main manifest by running one of the jar file

root@21979ab1759f:/task/src/task/com.achelos.task.tr03116ts/target# java -jar com.achelos.task.tr03116ts-1.0.1.jar --configFile ../../docker/GlobalConfig.xml --mics-file ../../data/input/ExampleMICS_SMGW-HAN-CLIENT.xml no main manifest attribute, in com.achelos.task.tr03116ts-1.0.1.jar

TLS 1.2 testcase cannot continue because of sending client hello with compression method

Issue Type: Tool Configuration

Testcase name: Session renegotiation

Testcase number: TLS_B1_FR_09

Test code: TLS_B1_FR_09.java

Description:
In TestRunPlan mode, the tool sends client hello packets carrying compression methond when it functions as TLS1.2 client. As a result, the handshake fails and the test cannot continue.

please reduce the involved programming languages

try to prevent no memory safe programming language like C

please offer a artefact with accurate collision resistant cryptographioc hash values like SHA-3-512

because of the compilation issues, plkease offer artefacts with accurate collision resistant cryptographioc hash values like SHA-3-512

	## License
	The TaSK framework is licensed under the EUPL-1.2-or-later.
	For more information on the license, see the included license text itself, or the according [website](https://joinup.ec.europa.eu/collection/eupl/eupl-text-eupl-12) of the European Commission.