-
Notifications
You must be signed in to change notification settings - Fork 18
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
improve secure-join message detection #473
Conversation
CI is failing because of unrelated file formatting, should be fixed by merging #474 first Would be nice to have at least one test for this fix. Changelog is managed manually in this repo, so PR needs a changelog entry. |
return False | ||
parts_count = 0 | ||
for part in message.iter_parts(): | ||
if parts_count == 0: |
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.
Could be flattened to if parts_count > 0: return False
, but otherwise the function looks good.
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.
improved the code to be easier to understand that what we are rejecting is when message has parts_count > 1
03039be
to
b2eaf1a
Compare
This needs rebase now that CI on the main is fixed. |
b6d49d2
to
704e464
Compare
Rebased it now |
be more strict in checking the secure-join special message structure
still missing: arbitrary Subject header is still allowed