-
Notifications
You must be signed in to change notification settings - Fork 24
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
HPCC4J-620 Jirabot: Sanitize information coming from external sources #720
Conversation
Jira Issue: https://hpccsystems.atlassian.net/browse/HPCC4J-620 Jirabot Action Result: |
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.
Discussed offline, but for bookeeping, it was decided emails would be sanitized via standard api/regex. If no efficient way to do this is quickly identified, we'll stop reporting emails in logs until a later fix.
@rpastrana Added code to handle email sanitization |
.github/workflows/Jirabot.yml
Outdated
# Return the email address only, returns '' if not valid or found | ||
return parseaddr(input)[1] | ||
else: | ||
return input |
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 could be considered a false positive, considering we don't know what format the input represents, it should return '' or an outright failure since email type is the only supported format.
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.
Good point
- Removed code that printed out untrusted information - Modified curl command to use more secure subprocess module Signed-off-by: James McMullan [email protected]
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.
@jpmcmu approved
Signed-off-by: James McMullan [email protected]
Type of change:
Checklist:
Testing: