BearSSL: fix hw accelerated SHA1#24397
Merged
s-hadinger merged 1 commit intoarendst:developmentfrom Jan 29, 2026
Merged
Conversation
Collaborator
|
Awesome. Thanks !!! |
josef109
pushed a commit
to josef109/Tasmota
that referenced
this pull request
Mar 15, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description:
This went unnoticed because Tasmota doesn’t currently use SHA-1.
I noticed it when streaming an H.264 camera feed from the ESP32-P4 to Chrome over WebSockets; the handshake failed.
HW acceleration is enabled by default for all (Tasmota) supported chips after the original ESP32.
Checklist:
NOTE: The code change must pass CI tests. Your PR cannot be merged unless tests pass