kern: Support for the non-Android boringssl library has been added. #555
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
You should know that the version management of boringssl is chaotic, divided into Android version and non-Android version, corresponding to two different code repositories. Also, the OPENSSL_VERSION_TEXT content has not been modified and remains unchanged. It is impossible to distinguish versions based on this field. Therefore, if you expect eCapture to better support the non-Android boringssl, you need to confirm the version matching situation by yourself. When necessary, you will need to patch it yourself. Android Boringssl: https://android.googlesource.com/platform/external/boringssl/ Non-Android Boringssl: https://boringssl.googlesource.com/boringssl aka https://github.com/google/boringssl Signed-off-by: CFC4N <cfc4n.cs@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
feat: #552
You should know that the version management of boringssl is chaotic, divided into Android version and non-Android version, corresponding to two different code repositories. Also, the
OPENSSL_VERSION_TEXTcontent has not been modified and remains unchanged. It is impossible to distinguish versions based on this field.Therefore, if you expect eCapture to better support the non-Android boringssl, you need to confirm the version matching situation by yourself. When necessary, you will need to patch it yourself.
Android Boringssl: https://android.googlesource.com/platform/external/boringssl/
Non-Android Boringssl: https://boringssl.googlesource.com/boringssl aka https://github.com/google/boringssl