-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manual testing - Deprecate Debian Stretch in Vulnerability Detector #3171
Comments
Review data
Testing environment
Tested packages
Status
|
Task resultsFresh InstallVD works as expected with Debian block active (no stretch). 🟢
VD works as expected with Debian block active (Stretch os added). 🟢
Update 4.4 to dev branchVD works as expected with Debian block active (no stretch). 🟢
VD works as expected with Debian block active (Stretch os added). 🟢
VD works as expected for other Debian OS version - Monitor Buster agent. 🟢
|
🟢 Everything seems to be working properly. It is proposed an improvement of the following description log, since it is produced when a system already deprecated (stretch) has been put, the message indicates that it has an unsupported version of Debian, but not which one.
It will be discussed with the development team and it will be decided whether to create an enhancement issue or not. Update: The following issue has been opened for this reason |
Description
With the changes applied in PR wazuh/wazuh#14542, the support for Debian Stretch in Vulnerablity Detector has been removed, so it is necessary to check that even with this change the other options of the module work correctly.
Proposed checks
stretch
specified).Warning
and does not scan the agent when specifyingstretch
.Steps to reproduce
Without the changes, when trying to scan a Debian Stretch agent, the following
Warning
will occur, as there is no vulnerability in the JSON feed:Configuration and considerations
Default VD configuration by activating the Debian block.
And specify (or not) the
<os>stretch</os>
target.The text was updated successfully, but these errors were encountered: