View Bug Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001232 | DCP-o-matic | Bugs | public | 2018-03-06 00:32 | 2018-10-17 20:15 |
Reporter | carl | Assigned To | carl | ||
Priority | urgent | Severity | crash | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Target Version | 2.12.0 | ||||
Summary | 0001232: Remaking an encrypted DCP in a project results in MXFs with unmatched IDs | ||||
Description |
| ||||
Tags | No tags attached. | ||||
Branch | |||||
Estimated weeks required | |||||
Estimated work required | Unknown | ||||
|
A bit exotic at first, but will this also happen when e.g. creating only a partial first DCP (e.g. with abort), and then continue, maybe multiple times?
|
|
I haven't investigated yet but I would guess so. Not all systems care about these IDs, I think. The problems I have seen so far are related to the HMAC used with encryption. |
|
Should be fixed by 5045742a5225e0771688ee3f8b6f8812bb1903fd in v2.12.x and d516d8e159e99d7b3b8250f39f976574df072cd8 in master. |
Date Modified | Username | Field | Change |
---|---|---|---|
2018-03-06 00:32 | carl | New Bug | |
2018-03-06 21:39 | Carsten | Note Added: 0002272 | |
2018-03-06 23:01 | carl | Note Added: 0002274 | |
2018-03-07 01:34 | carl | Description Updated | |
2018-03-07 14:23 | carl | Assigned To | => carl |
2018-03-07 14:23 | carl | Status | new => resolved |
2018-03-07 14:23 | carl | Resolution | open => fixed |
2018-03-07 14:23 | carl | Note Added: 0002281 | |
2018-10-17 20:15 | carl | Status | resolved => closed |