-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
signal: fix invalid certificate error in TLS handshake #2344
Labels
Comments
As a temporary workaround we might also want to flag all measurements from 2022-10-19 as failed until we deploy a fix to the probe |
hellais
added a commit
to ooni/probe-cli
that referenced
this issue
Oct 25, 2022
All measurements collected since 2022-10-19 with previous versions of OONI Probe will wrongly report sfu.voip.signal.org as blocked as it switched to using a different root CA This fixes: ooni/probe#2344
This was referenced Oct 25, 2022
bassosimone
pushed a commit
to ooni/probe-cli
that referenced
this issue
Oct 26, 2022
All measurements collected since 2022-10-19 with previous versions of OONI Probe will wrongly report sfu.voip.signal.org as blocked as it switched to using a different root CA This fixes: ooni/probe#2344
bassosimone
pushed a commit
to ooni/spec
that referenced
this issue
Oct 26, 2022
bassosimone
pushed a commit
to ooni/probe-cli
that referenced
this issue
Oct 26, 2022
This commit backports fa281f2 from the master branch to release/3.16. All measurements collected since 2022-10-19 with previous versions of OONI Probe will wrongly report sfu.voip.signal.org as blocked as it switched to using a different root CA This fixes: ooni/probe#2344
Apparently, we now witness a different error:
when using ooni/probe-cli@fa281f2 |
bassosimone
changed the title
signal-test: fix invalid certificate error in TLS handshake
signal: fix invalid certificate error in TLS handshake
Oct 31, 2022
bassosimone
added a commit
to ooni/probe-ios
that referenced
this issue
Oct 31, 2022
It won't probably be enough to fix the bug described at ooni/probe#2344, but it concludes the list of tasks related to v3.16.4. We'll probably need v3.16.5 for a more comprehensive fix.
bassosimone
added a commit
to ooni/probe-android
that referenced
this issue
Oct 31, 2022
It won't probably be enough to fix the bug described at ooni/probe#2344, but it concludes the list of tasks related to v3.16.4. We'll probably need v3.16.5 for a more comprehensive fix.
This was referenced Oct 31, 2022
bassosimone
pushed a commit
to ooni/probe-cli
that referenced
this issue
Oct 31, 2022
bassosimone
pushed a commit
to ooni/probe-cli
that referenced
this issue
Oct 31, 2022
This cherry picks 606bc93. See ooni/probe#2344
bassosimone
added a commit
to ooni/probe-ios
that referenced
this issue
Nov 1, 2022
This version contains a more comprehensive fix for the issue at ooni/probe#2344.
bassosimone
added a commit
to ooni/probe-android
that referenced
this issue
Nov 1, 2022
This version contains a more comprehensive fix for the issue at ooni/probe#2344.
bassosimone
added a commit
to ooni/probe-desktop
that referenced
this issue
Nov 1, 2022
Reference issue: ooni/probe#2344
bassosimone
pushed a commit
to ooni/spec
that referenced
this issue
Nov 1, 2022
It seems we implemented a more comprehensive fix now |
aanorbel
pushed a commit
to ooni/probe-ios
that referenced
this issue
Nov 2, 2022
* chore: use 3.16.5 This version contains a more comprehensive fix for the issue at ooni/probe#2344.
aanorbel
pushed a commit
to ooni/probe-android
that referenced
this issue
Nov 2, 2022
* chore: use 3.16.5 This version contains a more comprehensive fix for the issue at ooni/probe#2344.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It appears that since the 19th of October 2022, signal has changed the root CA they use to sign certificates for certain endpoints we test.
In particular the VOIP endpoint now sees this cert:
I believe this was added in February 2022 to the cert store of the android app through this commit: signalapp/Signal-Android@af3a39d.
While our test has a different CA: https://github.com/ooni/probe-cli/blob/e983a5cffb2f346c04f5187cde1f0b30b8a15781/internal/engine/experiment/signal/signal.go#L20
It's worth noting that the other endpoints are still on the old CA.
I guess the "easy" thing would be do just add this new root CA and consider it valid for both.
Alternatively we could just disable TLS validation entirely and delegate the job of figuring out if SSL is valid to the data processing pipeline, but this would give less accurate results in the app.
Yet another option, which is though much harder to implement, is to rely on a test helper which would have knowledge of what is the valid root CA and will perform the validation of the cert for the client.
I think we can start off with the easy fix of just adding this CA and then consider to do the other as future work.
The text was updated successfully, but these errors were encountered: