Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit fd8106f

Browse files
committedSep 17, 2021
Create an Eclipse OpenJ9 security policy
Signed-off-by: Peter Shipton <[email protected]>
1 parent 7d96165 commit fd8106f

File tree

1 file changed

+15
-0
lines changed

1 file changed

+15
-0
lines changed
 

‎SECURITY.md

+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
# Security Policy
2+
3+
Eclipse OpenJ9 follows the [Eclipse Vulnerability Reporting Policy](https://www.eclipse.org/security/policy.php). Vulnerabilities are tracked by the Eclipse OpenJ9 project leads, or by the Eclipse security team in cooperation with the OpenJ9 project leads. Fixing vulnerabilities is taken care of by the OpenJ9 project committers.
4+
5+
## Supported Versions
6+
7+
Eclipse OpenJ9 supports security updates only in upcoming OpenJ9 releases.
8+
9+
Since OpenJ9 currently uses a single stream to support the Long Term Support (LTS) releases of Java (8, 11 and 17) as well as the feature releases, fixes to the single OpenJ9 stream will be available in each of the next Java releases.
10+
11+
## Reporting a Vulnerability
12+
13+
In case of suspected vulnerabilities, we recommend that you do not use the OpenJ9 public issue tracker, but instead contact an Eclipse OpenJ9 project lead via the [OpenJ9 Slack](https://openj9.slack.com/) (join [here](https://join.slack.com/t/openj9/shared_invite/enQtNDU4MDI4Mjk0MTk2LWVhNTMzMGY1N2JkODQ1OWE0NTNmZjM4ZDcxOTBiMjk3NGFjM2U0ZDNhMmY0MDZlNzU0ZjAyNzQ1ODlmYjg3MjA)) and a private channel will be created for the discussion. Or contact the Eclipse Security Team via security@eclipse.org.
14+
15+
The project leads will ensure that a private bugzilla issue is created for any confirmed vulnerability to track the fixing of said issue.

0 commit comments

Comments
 (0)
Please sign in to comment.