View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011125 | GNUnet | util library | public | 2026-02-20 17:23 | 2026-02-20 17:23 |
| Reporter | thejackimonster | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | Git master | ||||
| Target Version | 0.27.0 | ||||
| Summary | 0011125: Multiple services are using the wrong peer identity key | ||||
| Description | Since the PILS service has been implemented, there are still multiple services and components in GNUnet which use the function `GNUNET_CRYPTO_eddsa_key_create_from_configuration()`. This function simply reads a private key for the peer from the a configuration instead of asking the PILS service about the current peer identity. This results in signature mismatches for example and other cryptographic issues. I'd suggest that we fully remove this function, replacing it with PILS integration. So that services like CADET, DHT, NSE, EXIT, REGEX and multiple TRANSPORT communicators work as intended again and they could react to peer identity changes. | ||||
| Steps To Reproduce | - enable logging to INFO level in the CADET service. - open any port with `gnunet-cadet -o $ANY_PORT` to start CADET if not running already - search for "CADET started for peer " in the log from CADET service - compare the peer identity in that line with the output from `gnunet-pils -1` | ||||
| Additional Information | Originally I was looking into CADET issues and noticed a signature verification failure. The CORE and TRANSPORT services were making a connection from one peer to another properly but CADET was using a different peer identity key for its signatures. So naturally it failed. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-02-20 17:23 | thejackimonster | New Issue |
