cameri / nostream / 41349169575

78%

push

github

feat(peering): authenticate peer relays with NIP-42  (#1030)

<!--- Provide a general summary of your changes in the Title above -->

## Description
<!--- Describe your changes in detail -->
This PR :- 
- Adds \`peering.peers[]\` (pubkey and relayUrl) as the
operator-configured trust list. Peers are identified by relay pubkey,
never by URL alone.
- Adds outbound NIP-42 AUTH signed with the relay's own keypair:
connect, wait for the challenge, send kind 22242, require \`OK true\`.
- Inbound: only a verified AUTH from an enabled configured pubkey marks
the connection as a peer. Unconfigured valid keys stay ordinary clients.
- Attaches the peer pubkey to connection state via
\`getPeerPubkey()\`/\`setPeerPubkey()\`; it expires with the NIP-42
session and clears on socket close.
- Documents relay key storage and the AUTH exchange in
\`docs/PEERING.md\`, plus the new settings in \`CONFIGURATION.md\`.

## Security
- Identity is proven only by signature verification; a URL or
self-declared key never grants peer status.
- Disabled/unconfigured peers get no recognition.
- Peer state is session-scoped, so an expired AUTH cannot retain peer
treatment.


## Related Issue
<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an
issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps
to reproduce -->
<!--- Please link to the issue here: -->
Closes :- #933

## Motivation and Context
<!--- Why is this change required? What problem does it solve? -->

## How Has This Been Tested?
<!--- Please describe in detail how you tested your changes. -->
<!--- Include details of your testing environment, and the tests you ran
to -->
<!--- see how your change affects other areas of the code, etc. -->

## Screenshots (if appropriate):

## Types of changes
<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->
- [ ] Non-func... (continued)

4501 of 6342 branches covered (70.97%)

Branch coverage included in aggregate %.

114 of 129 new or added lines in 4 files covered. (88.37%)

9792 of 12081 relevant lines covered (81.05%)

760.82 hits per line