-
-
Notifications
You must be signed in to change notification settings - Fork 964
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'main' into wall-dir-refactor-pr
- Loading branch information
Showing
616 changed files
with
29,644 additions
and
20,789 deletions.
There are no files selected for viewing
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
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
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
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
This file was deleted.
Oops, something went wrong.
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,32 +1,47 @@ | ||
| POLICY: Our security policy is to avoid leaving the ecosystem worse than we found it. Meaning we are not planning to introduce vulnerabilities into the ecosystem. | ||
| The OrcaSlicer team and community take all security bugs in OrcaSlicer seriously. Thank you for improving the security of OrcaSlicer. We appreciate your efforts to disclose the issue responsibly, and will make every effort to acknowledge your contributions. | ||
| # Security Policy | ||
|
|
||
| Report security bugs by emailing the lead maintainer at [email protected] and include the word "SECURITY" in the subject line. | ||
| At OrcaSlicer, we are committed to maintaining the security of our ecosystem. Our policy is to ensure that we do not introduce vulnerabilities and that any security issues are addressed promptly and responsibly. We appreciate your help in improving the security of OrcaSlicer and thank you for your responsible disclosure. | ||
| Reporting Security Bugs | ||
|
|
||
| The lead maintainer will acknowledge your email within a week (7 days), and will send a more detailed response up to 48 hours after that indicating the next steps in handling your report. After the initial reply to your report, the security team will endeavor to keep you informed of the progress towards a fix and an announcement. We may ask for additional information or guidance. | ||
| ## To report a security bug, please follow these guidelines: | ||
|
|
||
| OrcaSlicer will confirm the problem and determine the affected versions. | ||
| OrcaSlicer will audit code to find any similar problems. | ||
| OrcaSlicer will prepare fixes for all releases still under maintenance. These fixes will be released as fast as possible. | ||
| Report security bugs in third-party modules to the person or team maintaining the module. | ||
| * Email Security Bugs: | ||
| Send an email to the lead maintainer at [email protected]. | ||
| Include the word "SECURITY" in the subject line of your email. | ||
|
|
||
| SECURITY DISCLOSURE: Your responsibility is to report vulnerabilities to us using the guidelines outlined below. | ||
| Please give detailed steps on how to disclose the vulnerability. Keep these OWASP guidelines in mind ( https://www.owasp.org/index.php/Vulnerability_Disclosure_Cheat_Sheet ) when creating your disclosure policy. | ||
| * Response Times: | ||
| The lead maintainer will acknowledge receipt of your email within one week (7 days). | ||
| A detailed response will follow within 48 hours, outlining the next steps for handling your report. | ||
| After the initial reply, the security team will keep you informed about the progress toward a fix and any announcements. | ||
|
|
||
| Below are some recommendations for security disclosures: | ||
| * Information and Collaboration: | ||
| We may request additional information or guidance as we work on addressing the issue. | ||
|
|
||
| OrcaSlicer security contact { contact: mailto:[email protected]] } | ||
| When disclosing vulnerabilities please do the following: | ||
| Your name and affiliation (if any). | ||
| Include scope of vulnerability. Let us know who could use this exploit. | ||
| Document steps to identify the vulnerability. It is important that we can reproduce your findings. | ||
| Show how to exploit vulnerability, give us an attack scenario. | ||
| OrcaSlicer Checklist: Security Recommendations | ||
| Follow these steps to improve security when using OrcaSlicer. | ||
| * Handling the Report: | ||
| OrcaSlicer will confirm the problem and determine the affected versions. | ||
| We will audit the code to find any similar issues and prepare fixes for all releases still under maintenance. | ||
| Fixes will be released as quickly as possible. | ||
|
|
||
| ...SEE SOMETHING | ||
| ...SAY SOMETHING | ||
| 1)...SEE SOMETHING | ||
| We suggest you goto #2 if this happens. | ||
| * Third-Party Modules: | ||
| Report security issues in third-party modules to the respective maintainer of those modules. | ||
|
|
||
| Why? Through experience we have found it is best to goto #2 in this situation. | ||
| ## Security Disclosure Guidelines | ||
|
|
||
| When disclosing a vulnerability, please follow these steps to ensure your report is clear and actionable: | ||
|
|
||
| * Provide Detailed Information: | ||
| Scope: Clearly define the scope of the vulnerability. | ||
| Potential Impact: Let us know who could be affected by this exploit. | ||
| Reproduction Steps: Document detailed steps to reproduce the vulnerability. | ||
|
|
||
| Reference OWASP Guidelines: | ||
| Follow the <a href="https://cheatsheetseries.owasp.org/cheatsheets/Vulnerability_Disclosure_Cheat_Sheet.html">OWASP Vulnerability Disclosure Cheat Sheet</a> for best practices in vulnerability disclosure. | ||
|
|
||
| ## Security Recommendations | ||
|
|
||
| To enhance security when using OrcaSlicer, we recommend following these steps: | ||
|
|
||
| * SEE SOMETHING: If you notice anything suspicious or have concerns, please report it. | ||
| * SAY SOMETHING: If you have any doubts or need assistance, do not hesitate to contact us. | ||
|
|
||
| ### Thank you for your commitment to the security of OrcaSlicer. Your efforts help us maintain a safe and reliable ecosystem. |
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
Oops, something went wrong.