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
Deploying the probe-services backend for distributing openvpn IPs and credentials is not on the roadmap for the next few releases. We have shipped a hardcoded domain in the august release.
In some countries, DNS poisoning can be observed. We want to add a couple of fallback domains to the experiment. Additionally, having a way to easily distribute new IPs can allow us to verify if a block is based on an IP ban, 5-tuple rules, or use of DPI.
Three things are needed for this to happen:
Modify probe code to pick more endpoints, and keep iterating if domain resolution fails.
while working on this, I also gave more priority to possible oonirun
descriptors passed in the command line.
- Related: #2805
## Checklist
- [x] I have read the [contribution
guidelines](https://github.com/ooni/probe-cli/blob/master/CONTRIBUTING.md)
- [x] reference issue for this pull request:
ooni/probe#2805
- [ ] if you changed anything related to how experiments work and you
need to reflect these changes in the ooni/spec repository, please link
to the related ooni/spec pull request: <!-- add URL here -->
- [x] if you changed code inside an experiment, make sure you bump its
version number
## Description
Add fallback domains for openvpn default endpoints to be probed.
---------
Co-authored-by: DecFox <[email protected]>
Deploying the probe-services backend for distributing openvpn IPs and credentials is not on the roadmap for the next few releases. We have shipped a hardcoded domain in the august release.
In some countries, DNS poisoning can be observed. We want to add a couple of fallback domains to the experiment. Additionally, having a way to easily distribute new IPs can allow us to verify if a block is based on an IP ban, 5-tuple rules, or use of DPI.
Three things are needed for this to happen:
The text was updated successfully, but these errors were encountered: