View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0008766Compliance Test Tool (CTT) Unified Architecture1 - Script Issuepublic2023-03-31 08:402023-09-27 13:20
ReporterThomas Kugler Assigned ToPaul Hunkar  
PrioritynormalSeverityminorReproducibilityalways
Status assignedResolutionopen 
Summary0008766: SecureChannel cleanup
Description

DOS attack tests, e.g. Security > Security None > 007.js
The test is creating more SucureChannels than the server supports. Some of them are used by a Session. Others are expected to get closed by the server. It is expected that one (the last) unused SecureChannel is is not closed by the server. It should be legal that the server the server also closes this unused SecureChannel.

TagsNo tags attached.
Files Affected

Activities

Paul Hunkar

2023-04-13 15:24

administrator   ~0019174

We don't think this is allowed, but we want to better understand what you are asking for. Any channel can timeout and thus go away, but this test case is looking for what happens when no more secure channels are available, in which case the server is suppose to close the oldest secure channel that does not have a session on it. The last created secure channel should be available for creating a session, why are you closing the newest secure channel?

Thomas Kugler

2023-05-19 16:53

reporter   ~0019422

The unused secure channels are closed after a timeout. In the test this can happen (depending on the timing) also for the last unused secure channel.

Maximilian

2023-09-27 13:20

reporter   ~0020061

Since our DoS tests results haven't changed with the new CTT version (1.04.11), we would like to ask for a better description what is the expected behavior for secure channels in these tests.

"When creating a valid/real SecureChannel, prior [unused] channels should be clobbered."
Does this mean SecureChannels sould be reused?

Issue History

Date Modified Username Field Change
2023-03-31 08:40 Thomas Kugler New Issue
2023-04-13 15:24 Paul Hunkar Assigned To => Paul Hunkar
2023-04-13 15:24 Paul Hunkar Status new => feedback
2023-04-13 15:24 Paul Hunkar Note Added: 0019174
2023-05-19 16:53 Thomas Kugler Note Added: 0019422
2023-05-19 16:53 Thomas Kugler Status feedback => assigned
2023-09-27 13:20 Maximilian Note Added: 0020061