The following table lists the versions of Rootkit-Detector
that are actively supported with security updates:
Version | Supported |
---|---|
Latest (main) | ✅ |
Previous | ✅ |
Older | ❌ |
If you are using an unsupported version, we recommend upgrading to the latest version.
We take security vulnerabilities seriously. If you discover a security issue in Rootkit-Detector
, please report it privately to the maintainers. Do not disclose it publicly until we have addressed the issue.
- Contact Email: [INSERT EMAIL HERE]
- Subject: "Security Issue: [Brief Description]"
- Details to Include:
- Description of the vulnerability.
- Steps to reproduce the issue.
- Any relevant logs or screenshots.
- Affected version or commit hash.
- Acknowledgment: We will respond to your report within 3 business days.
- Resolution: We aim to resolve critical security issues within 14 days, depending on the severity and complexity.
To ensure the secure use of Rootkit-Detector
, follow these guidelines:
-
Run in a Trusted Environment:
- Ensure the system is properly secured before deploying
Rootkit-Detector
. - Use strong access controls for privileged commands.
- Ensure the system is properly secured before deploying
-
Regular Updates:
- Always use the latest version of
Rootkit-Detector
to benefit from security patches.
- Always use the latest version of
-
Kernel Module Security:
- Verify that all kernel modules (
.ko
files) are compiled from trusted source code. - Avoid loading third-party or unsigned kernel modules.
- Verify that all kernel modules (
-
Secure Communication:
- If using remote logging or interactions, ensure communication is encrypted (e.g., SSH, TLS).
-
Monitor Logs:
- Regularly monitor system logs (
dmesg
) for unusual activity flagged by the tool.
- Regularly monitor system logs (
We appreciate the efforts of the community to help us improve the security of Rootkit-Detector
. Special thanks to contributors who responsibly disclose vulnerabilities.