View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004961 | Taler | auditor | public | 2017-03-18 22:08 | 2018-04-15 18:34 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | 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 | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 0.5 | Fixed in Version | 0.5 | ||
| Summary | 0004961: check that aggregation records exist for deposits past payment deadline | ||||
| Description | Currently, the auditor does not check that aggregation records exist for deposits past their payment deadline (or that there was a full refund and thus there is no need for the deposit to appear in any aggregation). We check that all deposits are fine, and that all aggregations are supported by deposits, but not that the exchange actually bothered to run the aggregator. So basically an exchange where the aggergator is off would be certified as OK. (Which is true in the sense of it not being bankrupt, but...). We might want to do this as a separate tool from the main aggregator, especially as this is not about financial risk. Note that at the time that the auditor checks a deposit right now, the aggregation may not have applied, so this needs to be done as a separate pass by pay-deadline, which again suggests an independent tool might make sense. | ||||
| Tags | No tags attached. | ||||
| I've created a first exchangedb function to query for problematic deposits in 272f1135fca8bfd667dccc84f2bd6f31b7d2cc90 | |
| Implemented in 92d616b..8f48db8, ought to do another test (will do as part of 0005177 testing, thus resolving here). | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-03-18 22:08 | Christian Grothoff | New Issue | |
| 2017-03-18 22:08 | Christian Grothoff | Status | new => assigned |
| 2017-03-18 22:08 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2017-03-18 22:13 | Christian Grothoff | Assigned To | Christian Grothoff => |
| 2017-03-18 22:13 | Christian Grothoff | Status | assigned => implementing |
| 2017-03-18 22:25 | Christian Grothoff | Target Version | => 0.7.1 |
| 2017-04-08 22:09 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2017-04-08 22:09 | Christian Grothoff | Status | implementing => assigned |
| 2017-10-16 17:01 | Christian Grothoff | Note Added: 0012488 | |
| 2017-11-19 21:38 | Christian Grothoff | Note Added: 0012586 | |
| 2017-11-19 21:38 | Christian Grothoff | Status | assigned => informing |
| 2017-11-19 21:38 | Christian Grothoff | Resolution | open => fixed |
| 2017-11-19 21:38 | Christian Grothoff | Fixed in Version | => 0.5 |
| 2017-11-19 21:38 | Christian Grothoff | Target Version | 0.7.1 => 0.5 |
| 2018-04-15 18:34 | Christian Grothoff | Status | informing => closed |