nuts-foundation / nuts-foundation/nuts-node
Network: incorrectly configured nodes cause lots of logging
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 28
- Forks
- 23
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 76
Description
Due to authentication failures. These are logged on warn. Can happen on both inbound and outbound connections, but shouldn't cause log spam any more, since we fixed outbound connection backoff for auth failures. But out-of-date or misbehaving nodes can still cause this behavior, so it should still be fixed.
level=warning msg="Peer node DID could not be authenticated" did="did:nuts:6rK9cpmtiJY7fY5rB9p7LaJjwsAPhtHxjEzvZK8H1ZFj" error="none of the DNS names in the peer's TLS certificate match the NutsComm endpoint" module=Network peerAddr=20.238.131.33 peerAuthenticated=false peerDID= peerID=4719acd2-fcd1-40bf-8435-e72502b7b4fa
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by locating the network authentication warning for inbound and outbound connections, then trace how repeated authentication failures are logged. Done means misconfigured or out-of-date peers no longer cause log spam while authentication failures remain visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100