[mod] updated vendored bearssl to latest revision of upstream #11
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
|
I hope at some point zig fetch will support tls1.2, since I don't think adding git submodules to zig fetch is in scope for the tool. It would be great if we could stop vendoring upstream source |
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.
this sucks, we should somehow find out how to workaround upstream only supporting tlsv1.2 and zig fetch only tlsv1.3 or how to support zig fetch with submodules. vendoring this stuff with so much difference to upstream and not noticing this or keeping it up to date is a disaster waiting to go boom.