-
Notifications
You must be signed in to change notification settings - Fork 133
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
update to HackerOne reporting text #1675
Comments
SGTM |
I wonder if the following would be better: All reports should be be reproducible with standard Open Source tools (, e.g. bash, python, node.js scripts are acceptable, burp suite is not.) or include references to the specific source code relevant to the issue. Reports that can only be reproduced with non-open source tools and cannot otherwise be confirmed will be closed as "not applicable". |
I think we should mention including additional context using tools like burp suite is acceptable, but reproducible examples must use easy-to-use tools. Preferable, Node.js and Bash. |
@RafaelGSS that was along the lines of what I was trying to get at, so agree on that front. |
@RafaelGSS @mhdawson can you propose some amended text? |
How about: All reports should be be reproducible with standard Open Source tools (, e.g. bash, python, node.js scripts) or include references to the specific source code relevant to the issue. In order to supplement the report and provide additional context is is acceptable to use other tools. Reports that can only be reproduced with non-open source tools and cannot otherwise be confirmed will be closed as "not applicable". |
I propose we amend this paragraph
Adding:
The text was updated successfully, but these errors were encountered: