View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008100 | 10000-021: Device Onboarding | Spec | public | 2022-07-06 15:39 | 2022-09-21 20:19 |
| Reporter | David_Andover Smith | Assigned To | Randy Armstrong | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.05.02 RC1 | ||||
| Target Version | 1.05.02 | Fixed in Version | 1.05.02 | ||
| Summary | 0008100: Clarification of signature validation in ticket with multiple signatures | ||||
| Description | In Draft 52, section 6.4, there is some ambiguity on how to handle a ticket with an untrusted signature. How does one deal with a signature that may be rogue? ignore the one header or throw out the entire ticket? | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
Added statement |
|
|
Agreed to changes edited in F2F meeting. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-07-06 15:39 | David_Andover Smith | New Issue | |
| 2022-07-12 15:51 | Jim Luth | Target Version | => 1.05.02 |
| 2022-07-12 15:52 | Jim Luth | Assigned To | => Randy Armstrong |
| 2022-07-12 15:52 | Jim Luth | Status | new => assigned |
| 2022-09-11 04:52 | Randy Armstrong | Status | assigned => resolved |
| 2022-09-11 04:52 | Randy Armstrong | Resolution | open => fixed |
| 2022-09-11 04:52 | Randy Armstrong | Note Added: 0017622 | |
| 2022-09-21 20:19 | Jim Luth | Status | resolved => closed |
| 2022-09-21 20:19 | Jim Luth | Fixed in Version | => 1.05.02 |
| 2022-09-21 20:19 | Jim Luth | Note Added: 0017769 |
