ETSI's Bug Tracker - SECURITY | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0007334 | SECURITY | TSS&TP | public | 14-01-2016 13:08 | 18-01-2016 14:55 |
Reporter | haddads | ||||
Assigned To | Denis Filatov | ||||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | resolved | Resolution | fixed | ||
Platform | OS | OS Version | |||
Product Version | |||||
Target Version | Fixed in Version | ||||
Summary | 0007334: [TP_SEC_ITSS_SND_CAM_05_01_BV and 05_02] Formulation proposition | ||||
Description | Summary : "Check that The first CAM message sent more than one second after the last CAM message containing a field of type certificate also contain a field of type certificate" Proposition : with { the IUT being in the 'authorized' state and the IUT is configured to send more than one CAM per second and the IUT having sent a CAM containing header_fields['signer_info'].signer.type indicating 'certificate' contains header_fields['generation_time'] indicating TIME_LAST } ensure that { when { the IUT sends is requested to send its first SecuredMessage containing header_fields['its_aid'] indicating 'AID_CAM' and contains header_fields['generation_time'] indicating TIME (TIME >= TIME_LAST + 1sec) } then { this message contains header_fields['signer_info'].signer.type indicating 'certificate' } } And if you want to have two different tests with one where the IUT send other CAM messages within the next second or not. I think you can add in the "with" part : "and the IUT not sending any other messages during the next second" | ||||
Steps To Reproduce | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | |||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
14-01-2016 13:08 | haddads | New Issue | |||
14-01-2016 13:42 | haddads | Assigned To | => Denis Filatov | ||
14-01-2016 13:42 | haddads | Status | new => assigned | ||
18-01-2016 14:55 | Denis Filatov | Checkin | |||
18-01-2016 14:55 | Denis Filatov | Note Added: 0013719 | |||
18-01-2016 14:55 | Denis Filatov | Status | assigned => resolved | ||
18-01-2016 14:55 | Denis Filatov | Resolution | open => fixed |
Notes | |||||
|
|||||
|
|