-
Notifications
You must be signed in to change notification settings - Fork 11
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
Status of BoringSSL #307
Comments
Here are some notes on how we can make boringssl behave like other engines. |
Ideally, we can remove the additional seeds and cfg() options related to boringssl here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are still some things to do to fully support BoringSSL (#290) :
lto=true
cargo test
but the determinism is working when tested in a single threaded manner and also while fuzzing (thanks to the fact that libafl uses forks) (fixed in Fixing BoringSSL randomness in multithread execution #310)The text was updated successfully, but these errors were encountered: