View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007213 | GNUnet | messenger service | public | 2022-03-31 20:44 | 2022-09-26 18:54 |
| Reporter | thejackimonster | Assigned To | thejackimonster | Due Date | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | Git master | ||||
| Target Version | 0.17.0 | Fixed in Version | 0.17.6 | ||
| Summary | 0007213: Updating handle of messenger service does not do anything | ||||
| Description | Updating the messenger service handle is a function to allow optional forward secrecy and utilizing automatic chaining of the old and the new key for signing messages. Currently it seems like the function isn't doing anything besides reloading the same ego from identity service. This behavior is not intended. So I would flag this as not working. | ||||
| Steps To Reproduce | 1. Use any ego with the messenger service. 2. Call GNUNET_MESSENGER_update(). 3. Notice that the identity callback gets called as intended but the key and therefore the identity has not changed. | ||||
| Additional Information | This should get fixed inside of update_handle() in gnunet-service-messenger_handle.c! The ego store should have all necessary functionality to delete the old ego, create a new one with the same identifier and update the connected client handle information. | ||||
| Tags | No tags attached. | ||||
| The functionality of GNUNET_MESSENGER_update() is now implemented and seems to work. However renaming does not always work properly because the entries in the ego store will not be updated in all cases. So I will probably try to fix that before closing this issue. | |
| Renaming should now be fixed as well because the service will now avoid optimizing an ego lookup and instead check the identity service for accurate information. Just for transparency: The previous fix was done with commit "e95235a5f71aa40dea29a02cd8d4d1625add7d39" and the later fix with commit "d887cda509e0001adcdeb74feca80a71416827b7". | |
| Updating the key used by the messenger service is now implemented and renaming seems to work consistently. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-03-31 20:44 | thejackimonster | New Issue | |
| 2022-03-31 20:44 | thejackimonster | Status | new => assigned |
| 2022-03-31 20:44 | thejackimonster | Assigned To | => thejackimonster |
| 2022-04-02 18:10 | thejackimonster | Note Added: 0018850 | |
| 2022-04-05 20:50 | thejackimonster | Note Added: 0018853 | |
| 2022-04-05 20:52 | thejackimonster | Status | assigned => resolved |
| 2022-04-05 20:52 | thejackimonster | Resolution | open => fixed |
| 2022-04-05 20:52 | thejackimonster | Fixed in Version | => 0.16.4 |
| 2022-04-05 20:52 | thejackimonster | Note Added: 0018854 | |
| 2022-04-30 19:10 | schanzen | Target Version | 0.17.0 => 0.16.4 |
| 2022-06-04 21:13 | schanzen | Target Version | 0.16.4 => 0.17.0 |
| 2022-09-26 18:53 | Christian Grothoff | Fixed in Version | => 0.17.6 |
| 2022-09-26 18:54 | Christian Grothoff | Status | resolved => closed |