View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008293 | Taler | sandcastle (containerized demo deployment) | public | 2024-01-30 23:51 | 2024-08-28 21:30 |
| Reporter | Florian Dold | Assigned To | dvn | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | high | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Target Version | 0.13 | Fixed in Version | 0.13 | ||
| Summary | 0008293: put exchange master key into separate volume mount [estimate: 4h] | ||||
| Description | The master key should not change even if we nuke *everything* else, so it might make sense to put it into a different volume! | ||||
| Tags | No tags attached. | ||||
| I took several different approaches, most of which were trying to generalize the approach so that we could have a reusable function for making any file or directory persistent. I finally had the realization that it would be better to just simplify things and follow the preexisting pattern with the data directories but make it specific to the the exchange master key. The solution I came up with is here: https://git.taler.net/sandcastle-ng.git/commit/?h=dvn0/master-key-volume&id=28f87e2290b2623c3bd16ac41c52b9f4abdf060b It should migrate the key to the new persistent volume if it already exists, and if it's a new setup then it will put the key there to begin with. | |
| Merged into master here: https://git.taler.net/sandcastle-ng.git/commit/?id=3ae088af4b138878c97aa1295826c322daccf9c9 | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-01-30 23:51 | Florian Dold | New Issue | |
| 2024-01-30 23:51 | Florian Dold | Status | new => assigned |
| 2024-01-30 23:51 | Florian Dold | Assigned To | => dvn |
| 2024-03-05 10:23 | Florian Dold | Summary | consider putting exchange master key into separate volume => consider putting exchange master key and libeufin credentials into separate volume |
| 2024-03-05 10:23 | Florian Dold | Summary | consider putting exchange master key and libeufin credentials into separate volume => consider putting exchange master key into separate volume |
| 2024-03-05 10:24 | Florian Dold | Summary | consider putting exchange master key into separate volume => consider putting exchange master key and 2FA provider secrets (Telesign,...) into separate volume |
| 2024-04-08 12:32 | dvn | Summary | consider putting exchange master key and 2FA provider secrets (Telesign,...) into separate volume => consider putting exchange master key into separate volume |
| 2024-04-09 18:29 | dvn | Summary | consider putting exchange master key into separate volume => put exchange master key into separate volume mount |
| 2024-04-12 16:10 | Christian Grothoff | Priority | normal => high |
| 2024-04-12 16:10 | Christian Grothoff | Target Version | 0.10 => 0.11 |
| 2024-05-13 19:29 | Christian Grothoff | Target Version | 0.11 => 0.12 |
| 2024-06-24 00:52 | dvn | Summary | put exchange master key into separate volume mount => put exchange master key into separate volume mount [estimate: 4h] |
| 2024-06-26 16:09 | Christian Grothoff | Target Version | 0.12 => 0.13 |
| 2024-06-27 23:08 | dvn | Note Added: 0022751 | |
| 2024-06-28 12:38 | dvn | Status | assigned => informing |
| 2024-06-28 12:38 | dvn | Resolution | open => fixed |
| 2024-06-28 12:38 | dvn | Note Added: 0022761 | |
| 2024-08-26 20:30 | Christian Grothoff | Fixed in Version | => 0.13 |
| 2024-08-28 21:30 | Christian Grothoff | Status | informing => closed |