Skip to content
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

Open
1 of 4 tasks
aeyno opened this issue Mar 29, 2024 · 2 comments
Open
1 of 4 tasks

Status of BoringSSL #307

aeyno opened this issue Mar 29, 2024 · 2 comments

Comments

@aeyno
Copy link
Collaborator

aeyno commented Mar 29, 2024

There are still some things to do to fully support BoringSSL (#290) :

  • Debug builds with ASAN don't work without lto=true
  • The determinism test doesn't pass with multithreaded 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 security claims are not yet implemented
  • Some seeds are not working due to the way BoringSSL splits its handshake packets
@maxammann
Copy link
Contributor

  • Some seeds are not working due to the way BoringSSL splits its handshake packets

Here are some notes on how we can make boringssl behave like other engines.

#290 (comment)

@maxammann
Copy link
Contributor

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants