-
Notifications
You must be signed in to change notification settings - Fork 13
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Upgrade yarn.lock - Adapt changelog - Upgrade versions to 1.0.0 - Update security md
- Loading branch information
Showing
9 changed files
with
266 additions
and
279 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,25 +1,7 @@ | ||
<!--- https://www.eclipse.org/security/ ---> | ||
# Eclipse GLSP Vulnerability Reporting Policy | ||
|
||
_ISO 27005 defines vulnerability as: | ||
"A weakness of an asset or group of assets that can be exploited by one or more threats."_ | ||
If you think or suspect that you have discovered a new security vulnerability in this project, please do not disclose it on GitHub, e.g. in an issue, a PR, or a discussion. Any such disclosure will be removed/deleted on sight, to promote orderly disclosure, as per the Eclipse Foundation Security Policy (1). | ||
|
||
# Security Policy | ||
Instead, please report any potential vulnerability to the Eclipse Foundation Security Team. Make sure to provide a concise description of the issue, a CWE, and other supporting information. | ||
|
||
Eclipse GLSP follows the [Eclipse Vulnerability Reporting Policy](https://www.eclipse.org/security/policy.php). Vulnerabilities are tracked by the Eclipse security team, in cooperation with the GLSP project leads. Fixing vulnerabilities is taken care of by the GLSP committers, with assistance and guidance of the security team. | ||
|
||
## Reporting a Security Vulnerability | ||
|
||
We recommend that in case of suspected vulnerabilities you do not use the public issue tracker, but instead contact the Eclipse Security Team. | ||
|
||
The Eclipse Security Team provides help and advice to Eclipse projects on vulnerability issues and is the first point of contact for handling security vulnerabilities. | ||
Members of the Security Team are committers on Eclipse Projects and members of the Eclipse Architecture Council. You can contact the Eclipse Security Team via [[email protected]](mailto:[email protected]). Note that, as a matter of policy, the security team does not open attachments. | ||
|
||
Members of the Eclipse Security Team will receive messages sent to this address. | ||
This address should be used only for reporting undisclosed vulnerabilities; regular issue reports and questions unrelated to vulnerabilities in Eclipse software will be ignored. | ||
Note that this email address is not encrypted. | ||
|
||
## Disclosure | ||
|
||
Disclosure is initially limited to the reporter and all Eclipse Committers, but is expanded to include other individuals, and the general public. | ||
The timing and manner of disclosure is governed by the [Eclipse Security Policy](https://www.eclipse.org/security/policy.php). | ||
Publicly disclosed issues are listed on the [Disclosed Vulnerabilities Page](https://www.eclipse.org/security/known.php). | ||
(1) Eclipse Foundation Vulnerability Reporting Policy: <https://www.eclipse.org/security/policy.php> |
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 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
Oops, something went wrong.