You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
5
5
As part of Oracle's resolution to make Oracle Database Kubernetes-native (that is, observable and operable by Kubernetes), Oracle released _Oracle Database Operator for Kubernetes_ (`OraOperator` or the operator). OraOperator extends the Kubernetes API with custom resources and controllers for automating Oracle Database lifecycle management.
6
6
7
-
In this v0.2.0 release, `OraOperator` supports the following database configurations and infrastructure:
7
+
In this v0.2.1 release, `OraOperator` supports the following database configurations and infrastructure:
Copy file name to clipboardExpand all lines: SECURITY.md
+19-15Lines changed: 19 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,32 +1,36 @@
1
-
# Reporting Security Vulnerabilities
1
+
# Reporting security vulnerabilities
2
2
3
-
Oracle values the independent security research community, and believes that
4
-
responsible disclosure of security vulnerabilities helps us to ensure the security
5
-
and privacy of all of our users.
3
+
Oracle values the independent security research community and believes that
4
+
responsible disclosure of security vulnerabilities helps us ensure the security
5
+
and privacy of all our users.
6
6
7
7
Please do NOT raise a GitHub Issue to report a security vulnerability. If you
8
-
believe you have found a security vulnerability, then please submit a report to
8
+
believe you have found a security vulnerability, please submit a report to
9
9
[[email protected]][1] preferably with a proof of concept. Please review
10
10
some additional information on [how to report security vulnerabilities to Oracle][2].
11
-
Oracle encourages anyone who contacts Oracle Security to use email encryption, using
11
+
We encourage people who contact Oracle Security to use email encryption using
12
12
[our encryption key][3].
13
13
14
-
Please do not use other channels, or contact the project maintainers
14
+
We ask that you do not use other channels or contact the project maintainers
15
15
directly.
16
16
17
-
For non-vulnerability related security issues, including ideas for new or improved
18
-
security features, you are welcome to post these as GitHub Issues.
17
+
Non-vulnerability related security issues including ideas for new or improved
18
+
security featuresare welcome on GitHub Issues.
19
19
20
-
## Security Updates, Alerts and Bulletins
20
+
## Security updates, alerts and bulletins
21
21
22
-
Oracle issues security updates on a regular cadence. Many of our projects typically include release security fixes in conjunction with the [Oracle Critical Patch Update][3] program. Security updates are released on the
23
-
Tuesday closest to the 17th day of January, April, July and October. A pre-release announcement will be published on the Thursday preceding each release. Additional information, including past advisories, is available on our [security alerts][4]
22
+
Security updates will be released on a regular cadence. Many of our projects
23
+
will typically release security fixes in conjunction with the
information, including past advisories, is available on our [security alerts][4]
24
26
page.
25
27
26
-
## Security-Related Information
28
+
## Security-related information
27
29
28
-
Oracle will provide security-related information in our documentation. The information can be a threat model, best practices for secure use, or any known security issues. Please note
29
-
that labs and example code are intended to demonstrate a concept. These examples should not be used for production use without ensuring that the code is hardened, and in compliance with common security practices.
30
+
We will provide security related information such as a threat model, considerations
31
+
for secure use, or any known security issues in our documentation. Please note
32
+
that labs and sample code are intended to demonstrate a concept and may not be
0 commit comments