privacy: avoid exposing private RF propagation coordinates through overlay georeferencing

Aperta
  • Qualcosa non va?
#245 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Ferma
Stack tecnologico
python
Ambito
backend, security

Direzione di ricerca

Start with docs/features/rf_propagation/README.md and the rf_propagation_recompute view in nodes/views.py, then trace rf_propagation/tasks.py to see which coordinates reach the render and which bounds reach the API response. This is a privacy design task, so the first step is agreeing on a precision model for public bounds, not writing code. Done means a documented model, response tests for private-coordinate renders, and an overlay that still aligns usefully on the map.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Context

The RF propagation feature lets a radio node owner provide private, true coordinates for their node so the backend can render an accurate RF coverage map. The UI then overlays the generated PNG on a normal geographic map using the exact georeferenced bounds returned by the API.

This is related to the frontend alignment bug tracked in pskillen/meshtastic-bot-ui#204. While investigating that, we need to make sure any eventual alignment fix does not accidentally reveal the private transmitter coordinates.

Privacy concern

Today the render pipeline needs the true coordinates to calculate the correct RF map. Even if the PNG itself is low resolution, the API-provided overlay bounds and image placement may allow a client to infer the true transmitter location more precisely than intended, especially if the coverage pattern has a visible origin or if repeated renders can be compared.

The intended UX is that the public map should show a useful RF propagation approximation without betraying private node coordinates.

Possible approaches to investigate

  • Render with true coordinates, then post-process the PNG and georeferencing before exposing it.
  • Snap the exposed overlay anchor/bounds to a lower precision grid, then crop/pad/translate the raster so the visual alignment remains useful without exposing the private origin.
  • Add a privacy-preserving response contract, e.g. public display bounds that differ from internal render bounds, with documented precision guarantees.
  • Consider whether the origin-like visual features in the PNG itself need masking, blurring, cropping, or a minimum output resolution.
  • Ensure cache keys, filenames, metadata, logs, and API responses do not leak private coordinates directly or via overly precise georeferencing.

Acceptance criteria

  • The backend has a documented privacy model for RF renders based on private node coordinates.
  • API responses for RF propagation do not expose true private coordinates or exact private-coordinate-derived bounds beyond an agreed precision.
  • The frontend can still place the overlay accurately enough for the feature to be useful.
  • Existing and new renders remain cacheable without leaking private coordinate data via public identifiers or metadata.
  • Tests cover the public response contract for private-coordinate renders.

Notes

Current docs: docs/features/rf_propagation/README.md.
Relevant implementation areas likely include nodes/views.py::rf_propagation_recompute, rf_propagation/tasks.py, payload/hash generation, and render model serialization.

Lingua principale
Python
Stelle
1
Fork
0
Merge medio
23h 9m
PR unite (30g)
15

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pskillen/meshflow-api

Tutte le issue di pskillen/meshflow-api

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.