@@ -30,33 +30,42 @@ Starting with the Kea 1.7 release, all Kea versions with an odd minor
30
30
version number are development releases, and become EOL as soon as the
31
31
following stable release is published.
32
32
33
- Limited past EOL support may be available to higher tier customers.
33
+ Limited past EOL support may be available to higher- tier customers.
34
34
Please contact ISC sales, using this form: https://www.isc.org/contact/
35
35
36
36
## Reporting a Vulnerability
37
37
38
- To report security vulnerability, please follow this instruction:
38
+ To report a security vulnerability, please follow the instructions on this
39
+ page:
39
40
40
41
https://www.isc.org/reportbug/
41
42
42
- Briefly, we prefer confidential issue on gitlab (not github ). An issue is
43
+ We prefer a confidential issue on GitLab (not GitHub ). An issue is
43
44
much better, because it's easier to get more ISC engineers involved in it,
44
- evolve the case as more information is known, update or extra information, etc.
45
+ evolve the case as more information is known, update or add information, etc.
45
46
46
- Second best is to send e-mail (possibly encrypted) to kea-security@isc.org .
47
+ If a GitLab issue is not possible, please send e-mail (possibly encrypted)
48
+ to kea-security@isc.org .
47
49
48
- ## Software Defects and Security Vulnerability Disclosure Policy
50
+ ## Reporting a Bug
51
+
52
+ We are working with the interests of the greater Internet at heart, and we
53
+ hope you are too. In that vein, we do not offer bug bounties. If you think
54
+ you have found a bug in Kea, we encourage you to report it responsibly at the
55
+ link above; if verified, we will be happy to credit you in our Release Notes.
56
+
57
+ ## Software Defect and Security Vulnerability Disclosure Policy
49
58
50
59
ISC treats the security of its software products very seriously. This
51
- document discusses the evaluation of a defect severity and the process
60
+ document discusses the evaluation of a defect's severity and the process
52
61
in detail: https://kb.isc.org/docs/aa-00861
53
62
54
- ## Further reading
63
+ ## Further Reading
55
64
56
65
The ** Kea security** section of Kea ARM discusses the technical
57
- aspects, such as how to properly configure TLS certificates, how to secure
58
- Kea deployment and also what the security incident handling process
66
+ aspects, such as how to properly configure TLS certificates and how to secure
67
+ Kea deployment, and also what the security incident handling process
59
68
looks like: https://kea.readthedocs.io/en/latest/arm/security.html#kea-security-processes
60
69
61
- The ** Past advisories** for Kea can be found on the KB: https://kb.isc.org/docs
62
- On the left hand panel, see the ` Security Advisiories ` in the ` Kea DHCP ` section.
70
+ ** Past advisories** for Kea can be found in our KB: https://kb.isc.org/docs .
71
+ On the left- hand panel, see the ` Security Advisories ` in the ` Kea DHCP ` section.
0 commit comments