You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we assume that the update requests are not going to be tampered with as much as the measurement submit ones, we can use this to determine which inconsistencies are due to our geoip being off compared to the probe one, vs those which are due to the measurement metadata being inconsistent due to malice.
This can be done through the new update endpoint in the ooniprobe service, see #923, (
This is a follow up issue for #923
The Probe Update function in the old orchestra component logs useful metadata that we can use for anomaly detection. (see: https://github.com/ooni/orchestra/blob/master/registry/registry/handler/registry.go#L25)
If we assume that the update requests are not going to be tampered with as much as the measurement submit ones, we can use this to determine which inconsistencies are due to our geoip being off compared to the probe one, vs those which are due to the measurement metadata being inconsistent due to malice.
This can be done through the new update endpoint in the ooniprobe service, see #923, (
backend/ooniapi/services/ooniprobe/src/ooniprobe/routers/v1/probe_services.py
Line 130 in dcf48d5
The text was updated successfully, but these errors were encountered: