View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005823 | GNUnet | cadet service | public | 2019-08-01 20:02 | 2020-07-09 07:17 |
| Reporter | t3sserakt | Assigned To | t3sserakt | Due Date | |
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Target Version | 0.13.0 | Fixed in Version | 0.13.0 | ||
| Summary | 0005823: CADET message drop API for testing | ||||
| Description | The CADET monitoring API should be able to tell CADET to drop the next message of some type send from node A to node B. | ||||
| Additional Information | This shall help to write test cases for bug 0005822. | ||||
| Tags | No tags attached. | ||||
| How can I prevent misuse in a GNUnet multi user scenario. Can I check for the user who is using the cadet api? | |
| The service API is protected because the UNIX socket is only accessible to the user that started the service. So you do not need to worry about that. If the service is listening on a TCP socket, you can't have it. Any user is a valid user because he has access to the system. But that does not address the original issue right? I am unsure what exactly you are proposing and what you need it for. | |
| Introduced with d22eacb13 The CADET monitoring API no has functionality to drop any CADET message, when this is needed for testing. | |
| 0.13.0 released | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-08-01 20:02 | t3sserakt | New Issue | |
| 2019-08-01 20:02 | t3sserakt | Status | new => assigned |
| 2019-08-01 20:02 | t3sserakt | Assigned To | => t3sserakt |
| 2019-08-08 19:44 | t3sserakt | Note Added: 0014779 | |
| 2019-08-08 19:45 | t3sserakt | Note Edited: 0014779 | |
| 2019-08-13 06:02 | t3sserakt | Note Edited: 0014779 | |
| 2019-09-11 14:17 | schanzen | Note Added: 0014886 | |
| 2019-10-27 18:26 | schanzen | Target Version | 0.11.7 => 0.11.8 |
| 2019-11-04 22:05 | schanzen | Target Version | 0.11.8 => 0.11.9 |
| 2020-05-15 07:31 | schanzen | Target Version | => 0.13.0 |
| 2020-05-31 22:49 | Issue cloned: 0006284 | ||
| 2020-05-31 22:52 | Issue cloned: 0006331 | ||
| 2020-06-12 10:54 | t3sserakt | Status | assigned => resolved |
| 2020-06-12 10:54 | t3sserakt | Resolution | open => fixed |
| 2020-06-12 10:54 | t3sserakt | Fixed in Version | => 0.13.0 |
| 2020-06-12 10:54 | t3sserakt | Note Added: 0016261 | |
| 2020-07-09 07:17 | schanzen | Note Added: 0016415 | |
| 2020-07-09 07:17 | schanzen | Status | resolved => closed |