-
Notifications
You must be signed in to change notification settings - Fork 21.2k
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
fix(Telegram Trigger Node): Fix header secret check #12018
Merged
tomi
merged 1 commit into
master
from
node-2114-telegram-trigger-node-checking-x-telegram-bot-api-secret
Dec 3, 2024
Merged
fix(Telegram Trigger Node): Fix header secret check #12018
tomi
merged 1 commit into
master
from
node-2114-telegram-trigger-node-checking-x-telegram-bot-api-secret
Dec 3, 2024
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
`crypto.timingSafeEqual` throws if the given buffers are not of equal byte length. We don't want to throw but instead reject the webhook request.
Joffcom
approved these changes
Dec 3, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense, Thanks for fixing it.
n8n
|
Project |
n8n
|
Branch Review |
node-2114-telegram-trigger-node-checking-x-telegram-bot-api-secret
|
Run status |
|
Run duration | 04m 35s |
Commit |
|
Committer | Tomi Turtiainen |
View all properties for this run ↗︎ |
Test results | |
---|---|
|
0
|
|
1
|
|
0
|
|
0
|
|
478
|
View all changes introduced in this branch ↗︎ |
✅ All Cypress E2E specs passed |
Codecov ReportAttention: Patch coverage is
📢 Thoughts on this report? Let us know! |
Merged
Got released with |
riascho
pushed a commit
that referenced
this pull request
Jan 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
n8n team
Authored by the n8n team
node/improvement
New feature or request
Released
tests-needed
This PR needs additional tests
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.
Summary
crypto.timingSafeEqual
throws if the given buffers are not of equal byte length. We don't want to throw but instead reject the webhook request.Related Linear tickets, Github issues, and Community forum posts
https://community.n8n.io/t/n8n-1-68-1-69-docker-telegram-webhook-input-buffers-issue/62491/3
https://linear.app/n8n/issue/NODE-2114/telegram-trigger-node-checking-x-telegram-bot-api-secret-token
Review / Merge checklist
release/backport
(if the PR is an urgent fix that needs to be backported)