View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009205 | 10000-014: PubSub | Spec | public | 2023-10-16 11:47 | 2024-03-20 17:22 |
Reporter | Matthias Damm | Assigned To | Matthias Damm | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | 1.05.02 | ||||
Fixed in Version | 1.05.04 RC1 | ||||
Summary | 0009205: Unclear validity time of pubsub security keys | ||||
Description | It is not clear how long PubSub security keys can be used if it is not possible to get new keys from the SKS (e.g. SKS down, no network connection possible). 8.4.1 SecurityGroupType definition We have definitions for update behavior and update cycles e.g. check for next key in a cycle that is half the key lifetime. In Client/Server we define that update should start 1/3 before lifetime expires and keys are valid for 1/3 after lifetime expires. | ||||
Tags | No tags attached. | ||||
Commit Version | 1.05.04 RC | ||||
Fix Due Date | 2024-01-15 | ||||
|
6.2.12.2 SecurityGroupDataType Added following clarification: |
|
Agreed to changes edited in Dallas F2F. |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-10-16 11:47 | Matthias Damm | New Issue | |
2023-12-06 20:50 | Jim Luth | Assigned To | => Matthias Damm |
2023-12-06 20:50 | Jim Luth | Status | new => assigned |
2023-12-06 20:50 | Jim Luth | Commit Version | => 1.05.04 RC |
2023-12-06 20:50 | Jim Luth | Fix Due Date | => 2024-01-15 |
2024-03-18 00:20 | Matthias Damm | Status | assigned => resolved |
2024-03-18 00:20 | Matthias Damm | Resolution | open => fixed |
2024-03-18 00:20 | Matthias Damm | Fixed in Version | => 1.05.04 RC1 |
2024-03-18 00:20 | Matthias Damm | Note Added: 0020923 | |
2024-03-20 17:22 | Jim Luth | Status | resolved => closed |
2024-03-20 17:22 | Jim Luth | Note Added: 0020981 |