-
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
oocrypto: AES not used on darwin/arm64 #2122
Comments
See ooni/probe#2122 for context.
Turns out |
We may also want to consider https://github.com/klauspost/cpuid |
It turns out the problem described in ooni/probe#2122 only affects darwin/arm64, so we should be good to re-enable Android.
It turns out the problem described in ooni/probe#2122 only affects darwin/arm64, so we should be good to re-enable Android.
This diff ensures we hardcode the capabilities of darwin/arm64. While there, strive to make the packages naming slightly less confusing. Reference issue: ooni/probe#2122. Surpersedes (and draws from) #5. Co-authored-by: ain ghazal <[email protected]>
I'm going to merge the fix at ooni/oocrypto#7, which is based on the previous diff by @ainghazal at ooni/oocrypto#5 and includes improvements in naming and documentation that should dispel some ambiguity that @ainghazal mentioned in private to me while we were discussing this issue. |
This diff ensures we hardcode the capabilities of darwin/arm64. While there, strive to make the packages naming slightly less confusing. Reference issue: ooni/probe#2122. Surpersedes (and draws from) #5. Co-authored-by: ain ghazal [email protected] Co-authored-by: ain ghazal <[email protected]>
This diff backports code to correctly handle darwin/arm64 from `main` (see #7). While there, this diff aims at reducing unnecessary differences with the main branch, by removing code we also removed in there. The reference issues are: 1. ooni/probe#2122 2. ooni/probe#2223
This diff backports code to correctly handle darwin/arm64 from `main` (see #7). While there, this diff aims at reducing unnecessary differences with the main branch, by removing code we also removed in there. The reference issues are: 1. ooni/probe#2122 2. ooni/probe#2223
This ensures we keep ooni/probe#2122 fixed.
* chore: use {go,oohttp,oocrypto} v1.18.5 This diff pins OONI to use go1.18.5 and oohttp and oocrypto at go1.18.5 as the version of go with which we build releases. The same codebase also works with go1.19 although this configuration cannot include Psiphon (see ooni/probe#2222). Closes ooni/probe#2223. * fix: use [email protected] This ensures we keep ooni/probe#2122 fixed.
This issue is about oocrypto being broken and not using AES on darwin/arm64. Most likely, this means that the way in which we're trying to pick up CPU features does not work. So, for example this measurement using the 3.15 release candidate uses
TLS_AES_128_GCM_SHA256
. Conversely, this measurement using the development branch usesTLS_CHACHA20_POLY1305_SHA256
. We should probably stop using oocrypto until we understand why it's not working as intended and possibly consider reverting back to ooni/go instead.The text was updated successfully, but these errors were encountered: