Skip to content
This repository was archived by the owner on Dec 17, 2021. It is now read-only.

Commit 8dee640

Browse files
authored
feat: release beta 3 (#21)
1 parent 74f7892 commit 8dee640

File tree

2 files changed

+5
-5
lines changed

2 files changed

+5
-5
lines changed

.circleci/config.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
#Splunk Connect for Syslog (SC4S) by Splunk, Inc.
1+
#Splunk Connect for SNMP by Splunk, Inc.
22
#
33
#To the extent possible under law, the person who associated CC0 with
4-
#Splunk Connect for Syslog (SC4S) has waived all copyright and related or neighboring rights
5-
#to Splunk Connect for Syslog (SC4S).
4+
#Splunk Connect for SNMP has waived all copyright and related or neighboring rights
5+
#to Splunk Connect for SNMP.
66
#
77
#You should have received a copy of the CC0 legalcode along with this
88
#work. If not, see <http://creativecommons.org/publicdomain/zero/1.0/>.

SECURITY.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,13 +2,13 @@
22

33
## Supported Versions
44

5-
Splunk Connect for Syslog does not support "hotfix" patching, so all bug fixes (including security issues) are contained within the latest GA release.
5+
Splunk Connect for SNMP does not support "hotfix" patching, so all bug fixes (including security issues) are contained within the latest GA release.
66

77
## Reporting a Vulnerability
88

99
Splunk takes security vulnerabilities very seriously. When a member of the community identifies a potential security issue, it needs to be reported fully and carefully. A diligent Community helps keep us all safer and Splunk appreciates your timely and responsible disclosure of any security concern.
1010

11-
To report a potential vulnerability in Splunk Connect for Syslog, please contact the Splunk Product Security Team via the Splunk website:
11+
To report a potential vulnerability in Splunk Connect for SNMP, please contact the Splunk Product Security Team via the Splunk website:
1212
https://www.splunk.com/en_us/form/bug-submission-prodsec.html
1313

1414
Per the Splunk Product Security Policy, A Splunk representative will be in touch with you within 2 business days of receipt of your communication.

0 commit comments

Comments
 (0)