Skip to content

OONI Probe CLI v3.7.0
Compare
Choose a tag to compare
@bassosimone bassosimone released this 08 Mar 13:04
· 1352 commits to master since this release
v3.7.0
This tag was signed with the committer’s verified signature. The key has expired.
bassosimone Simone Basso
GPG key ID: 80B691277733D95B
Expired
Learn about vigilant mode.
784d3d0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

iOS

pod 'oonimkall', :podspec => 'https://dl.bintray.com/ooni/ios/oonimkall-2021.03.08-125957.podspec'

Android

implementation 'org.ooni:oonimkall:2021.03.08-130053'

Generic build instructions

go run ./internal/cmd/getresources
go build -v $extraBuildFlags ./cmd/ooniprobe

Changes

  • 🔨 👀 We moved the Signal messenger experiment into the experimental nettest group. So, if you wanna run this experiment, you now need to run ooniprobe run experimental. We will keep this experiment into this group until the desktop app has a UI for it. We don't want the desktop app to run experiments for which there is no UI.

  • ✨ We added dnscheck and stunreachability to the experimental nettest group. This is part of an effort to start exposing more experimental tests to users. For now, this group is only available to CLI users.

  • 🐛 webconnectivity now fails less badly when asked to test for https://1.1.1.1. Before the whole test failed, now only the control step fails because the legacy control endpoint does not support this use case. This enhancement would still enable us to draw conclusions regarding whether https://1.1.1.1 is blocked, even though the UI will show a failed experiment.

  • 🐛 windows: ooniprobe run unattended now only tests a handful of URLs, like we do on macOS.

  • 🔨 we have merged code that improves how we communicate with out backend. This code is currently not used by ooniprobe but its presence already allows us to check whether our definition of the API spec is in sync with the backend. We will take advantage of this improvement in subsequent releases, when we'll start using the new code.

Assets 11
Loading