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

Add option to allow building with BoringSSL #738

Closed
wants to merge 1 commit into from

Conversation

nacho
Copy link
Contributor

@nacho nacho commented Oct 31, 2023

To build with BoringSSL CRYPTO_INCLUDE_DIRS
and CRYPTO_LIBRARY_DIRS must be defined

Also fix all the compile issues when building
with BoringSSL

To build with BoringSSL CRYPTO_INCLUDE_DIRS
and CRYPTO_LIBRARY_DIRS must be defined

Also fix all the compile issues when building
with BoringSSL
@nacho
Copy link
Contributor Author

nacho commented Nov 2, 2023

I went at the end for a more conservative approach given the CI failures. We can revisit it later on. Can you please approve again the run? Thanks

@LDVG
Copy link
Contributor

LDVG commented Nov 2, 2023

Hi,

Thank you for your patch. While we're generally not opposed to an idea like this, maintaining support for BoringSSL which has no guarantees of API stability is a fairly heavy burden. It might make more sense for us to refactor libfido2 to use a thin crypto abstraction layer that is statically linked. That would make it easier for a third party to write their own wrapper to use something else if they prefer. This has been discussed previously in the context of other crypto libraries.

@nacho
Copy link
Contributor Author

nacho commented Nov 2, 2023

Sounds fair, thanks for the comment

@nacho nacho closed this Nov 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants