View Issue Details

IDProjectCategoryView StatusLast Update
0005119Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2022-03-18 15:26
ReporterJayanth Velusamy Assigned ToSebastian Allmendinger  
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionfixed 
Product Version1.03.341.389 
Fixed in Version1.03.341.391 
Summary0005119: Reducing number of session and secure channel for embedded profiles
Description

For embedded systems with smaller memory footprints, the number of secure channel (maxChannels) and session (maxSession) will be lower.

In the test case Security/Security None/007.js, when the channel count is less than 95, the test case will add 5 more channel for DoS attack checking. The Max SecureChannels and Max Supported Sessions configured in "/Server Test/Capabilities/Max SecureChannels" and "/Server Test/Capabilities/Max Supported Sessions".

Embedded targets should be allowed to have lower numbers such as Max SecureChannels = 2 and Max Supported Sessions = 1. There should be exemption for embedded profile for these kind of test cases.

We have also tested this test case in CTT version (1.03.341.390)

TagsNo tags attached.
Files Affected

Relationships

has duplicate 0004735 closedAlexander Allmendinger DOS test case does not wait until channel expires 

Activities

Sebastian Allmendinger

2019-11-21 07:38

developer   ~0011253

The script was already using the number of Sessions and SecureChannels defined in the CTT settings.
Due to the limitations of the CTT, it only uses 95 SecureChannel and Sessions if the number in the setting "/Server Test/Capabilities/Max SecureChannels" is >= 95 or 0 (which means unlimited).
In the next version of the CTT a new setting is introduced:
"/Server Test/Secure Channel/Min Lifetime of SecureChannel"
which allows to define a delay between the creation of the unused SecureChannel. The default value is set accordingly to the actual delay in the test script (1000 ms).

Paul Hunkar

2020-07-03 17:09

administrator   ~0012548

reviewed in CMP call

Issue History

Date Modified Username Field Change
2019-10-01 13:19 Jayanth Velusamy New Issue
2019-10-04 15:25 Paul Hunkar Assigned To => Alexander Allmendinger
2019-10-04 15:25 Paul Hunkar Status new => assigned
2019-11-07 14:44 Alexander Allmendinger Assigned To Alexander Allmendinger => Sebastian Allmendinger
2019-11-21 07:38 Sebastian Allmendinger Status assigned => resolved
2019-11-21 07:38 Sebastian Allmendinger Resolution open => fixed
2019-11-21 07:38 Sebastian Allmendinger Fixed in Version => 1.03.341.391
2019-11-21 07:38 Sebastian Allmendinger Note Added: 0011253
2020-07-03 17:09 Paul Hunkar Status resolved => closed
2020-07-03 17:09 Paul Hunkar Note Added: 0012548
2022-03-18 15:26 Sebastian Allmendinger Relationship added has duplicate 0004735