-----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEc4h3qmyCnyakMcX0gLaRJ3cz2VsFAmBuKF8ACgkQgLaRJ3cz 2VuQ2w/+OCLSkAddq5IJ8mMieqY1/oDm3KlsVifXN4yrWNT9MGip0Fh5hns6tRir tGFOJ2FuG/3czAk60pkJW3n1m2pUU0pR6/55VtwBVyLrbYhtCWb0R9N2g46Ru2UN YN3Cl19XCmBdUByj30zFW1eyfdpO1eZzn+BOpU8oRL+xm2jm4iCGebxM/i2/rxRn Lq20Wj2ubJQYbi43i0Gos9gtaNM1JAZQHYrXUxD2B8B/raq2+toggV+NNkJzu8VM uh0126nUdEzR1mMs9nUav+wvyFrjpaHZ8EHzsCk91KtICVFFyCjZGkkNCOqG4dJb cz3DU4vI41CcWLVgs+urPQ66RstKKOev0VXDhUF4w9aKs88Ya40NJj4qeoJRZNnR nZY/aFRRl3dqwbCX7LpRLl8HSSb02e5hkiv2wtiEpvk6z1K/N7F3C0CxCTc5Wxwv +vTDM4zLi9WCT5kxkRJ/1lbYNUV/9jqsSOmsQOMf+dqmyA0bxSk/zXMxagLwMe5D hClM5/r+pFirc+/tKcECRyyw60YL19VzIY1hlq2YlFO3b/9zsZe0ssaRE1qQL0w8 EjAe4nTiXIw28Js6R5lbnwK/LbyZIleRK3xYgDRA0RNDVvGMk+cxxUqJfP/ECdnD sSOFdJAVU5gEOU9smPa9Nx9746nigEK5JjCuR/7cNOcW1Jcit5o= =G2QR -----END PGP SIGNATURE----- Merge tag 'v3.9.2' into stable ooni/probe-cli v3.9.2
OONI Probe Client Library and CLI
The next generation OONI Probe: client library and Command Line Interface.
User setup
Please, follow the instructions at ooni.org/install/cli
to install ooniprobe. If we do not support your use case, please let us know.
Once ooniprobe is installed, try ooniprobe help to get interactive help.
Reporting issues
Please, report issues with this codebase at github.com/ooni/probe.
Please, make sure you tag such issues using the ooni/probe-cli label.
Repository organization
Every top-level directory contains an explanatory README file.
Development setup
Be sure you have golang >= 1.16 and a C compiler (when developing for Windows, you need Mingw-w64 installed). You can build using:
go build -v ./cmd/ooniprobe
This will generate a binary called ooniprobe in the current directory.
Android bindings
./build-android.bash
We automatically build Android bindings whenever commits are pushed to the
mobile-staging branch. Such builds could be integrated by using:
implementation "org.ooni:oonimkall:VERSION"
Where VERSION is like 2020.03.30-231914 corresponding to the
time when the build occurred.
iOS bindings
./build-ios.bash
We automatically build iOS bindings whenever commits are pushed to the
mobile-staging branch. Such builds could be integrated by using:
pod 'oonimkall', :podspec => 'https://dl.bintray.com/ooni/ios/oonimkall-VERSION.podspec'
Where VERSION is like 2020.03.30-231914 corresponding to the
time when the build occurred.
Updating dependencies
go get -u -v ./... && go mod tidy
Releasing
Create an issue according to the routine release template and perform any item inside the check-list.