From 06aa5943c6fa1a551ce8979ce2f4d75cc50caacb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E0=B8=99=E0=B8=B2=E0=B8=A2=2E=E0=B8=9E=E0=B8=87=E0=B8=A9?= =?UTF-8?q?=E0=B9=8C=E0=B8=98=E0=B8=A7=E0=B8=B1=E0=B8=95=20=E0=B9=80?= =?UTF-8?q?=E0=B8=81=E0=B8=B0=E0=B8=AA=E0=B8=B9=E0=B8=87=E0=B9=80=E0=B8=99?= =?UTF-8?q?=E0=B8=B4=E0=B8=99?= <42609004+phongthawat@users.noreply.github.com> Date: Tue, 21 Feb 2023 01:46:09 +0700 Subject: [PATCH] TTS https://smart-lab.ru/blog/news/879226.php#comment15342993 --- SECURITY.TTS | 31 +++++++++++++++++++++++++++++++ SECURITY.md | 31 ------------------------------- 2 files changed, 31 insertions(+), 31 deletions(-) create mode 100644 SECURITY.TTS delete mode 100644 SECURITY.md diff --git a/SECURITY.TTS b/SECURITY.TTS new file mode 100644 index 0000000..d9a8762 --- /dev/null +++ b/SECURITY.TTS @@ -0,0 +1,31 @@ +Thanks for helping make GitHub safe for everyone. + +## Security + +GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub). + +Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation. + +## Reporting Security Issues + +If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure. + +**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.** + +Instead, please send an email to opensource-security[@]github.com. + +Please include as much of the information listed below as you can to help us better understand and resolve the issue: + + * The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting) + * Full paths of source file(s) related to the manifestation of the issue + * The location of the affected source code (tag/branch/commit or direct URL) + * Any special configuration required to reproduce the issue + * Step-by-step instructions to reproduce the issue + * Proof-of-concept or exploit code (if possible) + * Impact of the issue, including how an attacker might exploit the issue + +This information will help us triage your report more quickly. + +## Policy + +See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor) diff --git a/SECURITY.md b/SECURITY.md deleted file mode 100644 index d9a8762..0000000 --- a/SECURITY.md +++ /dev/null @@ -1,31 +0,0 @@ -Thanks for helping make GitHub safe for everyone. - -## Security - -GitHub takes the security of our software products and services seriously, including all of the open source code repositories managed through our GitHub organizations, such as [GitHub](https://github.com/GitHub). - -Even though [open source repositories are outside of the scope of our bug bounty program](https://bounty.github.com/index.html#scope) and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation. - -## Reporting Security Issues - -If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure. - -**Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.** - -Instead, please send an email to opensource-security[@]github.com. - -Please include as much of the information listed below as you can to help us better understand and resolve the issue: - - * The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting) - * Full paths of source file(s) related to the manifestation of the issue - * The location of the affected source code (tag/branch/commit or direct URL) - * Any special configuration required to reproduce the issue - * Step-by-step instructions to reproduce the issue - * Proof-of-concept or exploit code (if possible) - * Impact of the issue, including how an attacker might exploit the issue - -This information will help us triage your report more quickly. - -## Policy - -See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor)