QNT should allow controlling exactly which addresses are probed

Open
#790 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
rust

Research direction

Start with the QNT API and the Connection::get_remote_nat_traversal_addresses call mentioned in the issue. Define an API that lets applications restrict probe destinations even when advertised candidates change after that call; done means remote input can no longer choose arbitrary probe addresses while valid NAT traversal remains possible.

Written by the indexing model from the issue text.

Description

API QNT

Currently the QNT API probes all addresses supplied by the remote. Including any that point to e.g. documentation domains, test domains, private networks etc.

Not having any control over which addresses are used for probes means that the remote can directly control where NAT probes are sent, potentially directing probes at intentionally wrong places. Having an API which explicitly allows controlling which remote addresses NAT probes are sent to might help.

When designing this API bear in mind that the application will not always have the full up-to-date view of all advertised addresses. The address candidates can change as soon as the Connection::get_remote_nat_traversal_addresses call has returned and before another API has been called.

Dominant language
Rust
Stars
454
Forks
98
Avg merge
2d 8h
Merged PRs (30d)
19

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from n0-computer/noq

All issues in n0-computer/noq

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.