View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008206 | GNUnet | core service | public | 2024-01-22 18:17 | 2024-01-26 16:27 |
| Reporter | ch3 | Assigned To | Christian Grothoff | ||
| Priority | normal | Severity | minor | Reproducibility | N/A |
| Status | assigned | Resolution | open | ||
| Summary | 0008206: Core should take all ownership of Peer Identities | ||||
| Description | As peer ids will become more dynamic (they will change on address changes) one single service should take ownership on managing them. This will be core. Implications on transport, which currently uses peer ids (pids) to validate/sign queues: - In the future it will validate queues by asking core to sign the provided challenge. - It will generate its own key for each address it manages. Implications on hellos: - hellos need to include transport's per-address-key Implications on core: - core will be responsible to create, sign and store the hello in peerstore - needs to provide api functionality to do things pid-related (sign challenges, inform about pid change, ...) | ||||
| Tags | No tags attached. | ||||
|
|
Christian, can you please review this issue or assign it for review by and to Martin? |
|
|
From re-reading this, it is unclear to me why we have the same key for both: 1. the secure channel established by core 2. the "validation" of a queue Can't we consolidate this into one? Can core do both? I particularly do not like the fact that the above text hints at either sending transport private keys or offering a gerneral signing API. |
