mirror of
https://github.com/isc-projects/bind9.git
synced 2026-05-04 17:24:47 -04:00
2c20f23b69
Rework the Security Incident Handling Checklist so that it does not only contain the SWENG-side steps for handling a security incident, but also all the other steps required by ISC procedures.
46 lines
1.2 KiB
Markdown
46 lines
1.2 KiB
Markdown
<!--
|
|
If the bug you are reporting is potentially security-related - for example,
|
|
if it involves an assertion failure or other crash in `named` that can be
|
|
triggered repeatedly - then please make sure that you make the new issue
|
|
confidential!
|
|
-->
|
|
|
|
### Summary
|
|
|
|
(Summarize the bug encountered concisely.)
|
|
|
|
### BIND version used
|
|
|
|
(Paste the output of `named -V`.)
|
|
|
|
### Steps to reproduce
|
|
|
|
(How one can reproduce the issue - this is very important.)
|
|
|
|
### What is the current *bug* behavior?
|
|
|
|
(What actually happens.)
|
|
|
|
### What is the expected *correct* behavior?
|
|
|
|
(What you should see instead.)
|
|
|
|
### Relevant configuration files
|
|
|
|
(Paste any relevant configuration files - please use code blocks (```)
|
|
to format console output. If submitting the contents of your
|
|
configuration file in a non-confidential Issue, it is advisable to
|
|
obscure key secrets: this can be done automatically by using
|
|
`named-checkconf -px`.)
|
|
|
|
### Relevant logs and/or screenshots
|
|
|
|
(Paste any relevant logs - please use code blocks (```) to format console
|
|
output, logs, and code, as it's very hard to read otherwise.)
|
|
|
|
### Possible fixes
|
|
|
|
(If you can, link to the line of code that might be responsible for the
|
|
problem.)
|
|
|
|
/label ~bug
|