Check the plugin file name

Oct 13, 2025 by recoveryshake.com 63 views

Introduction

Lynis is a powerful security auditing tool that helps system administrators and security professionals identify vulnerabilities and weaknesses in their systems. However, like any other tool, Lynis is not immune to bugs and issues. In this article, we will discuss a specific issue with Lynis version 3.1.4, where it alters the phase2 plugin filename, making it unable to be used.

Bug Description

While importing a phase2 plugin by Lynis, there seem to be an issue with file naming. Lynis adds "plugin" and "phase2" to the beginning and end of the file name. This issue is not specific to a particular plugin, but rather a general problem with the way Lynis handles phase2 plugin filenames.

Version

The issue was encountered on the following versions:

Distribution: Ubuntu 22.04.5
Lynis version: 3.1.4

Expected Behavior

The expected behavior of Lynis is to read the custom plugin file provided in the appropriate directory mentioned in the documentation. However, due to the issue with file naming, Lynis is unable to read the plugin file correctly.

Output

The output of Lynis when trying to import the phase2 plugin is as follows:

2025-03-09 16:55:47 Action: Performing plugin tests 2025-03-09 16:55:47 Found plugin file: /usr/share/lynis/plugins/plugin_advanced_firewall_check_phase2 2025-03-09 16:55:47 Action: checking plugin status in profile: /etc/lynis/default.prf 2025-03-09 16:55:47 Result: plugin enabled in profile (/etc/lynis/default.prf) 2025-03-09 16:55:47 Result: plugin plugin_advanced_firewall_check_phase2 is enabled 2025-03-09 16:55:47 Plugin plugin_advanced_firewall_check_phase2: Skipped for phase 2 (no file found: /usr/share/lynis/plugins/plugin_plugin_advanced_firewall_check_phase2_phase2) 2025-03-09 16:55:47 -- 2025-03-09 16:55:47 Result: Found 0 plugins of which 0 are enabled 2025-03-09 16:55:47 Result: Plugins phase 2 finished

Additional Context

The issue was encountered after checking all the troubleshooting points in the Lynis documentation. The plugin file was placed in the correct directory, and the plugin was enabled in the profile. However, despite these efforts, Lynis was unable to read the plugin file correctly.

Troubleshooting Steps

To troubleshoot this issue, the following steps can be taken:

Check the plugin file name: Ensure that the plugin file name is correct and does not contain any extra characters.
Check the plugin directory: Verify that the plugin file is placed in the correct directory.
Check the plugin profile: Ensure that the plugin is enabled in the profile.
Check the Lynis version: Verify that the Lynis version is up-to-date.

Conclusion

In conclusion, the issue with Lynis altering the phase2 plugin filename making it unable to be used is a specific problem with the way Lynis handles phase2 plugin filenames. The issue was encountered on Lynis version 3.1.4, and the troubleshooting steps outlined above can be taken to resolve the issue. It is essential to ensure that the plugin file name is correct, the plugin directory is correct, and the plugin is enabled in the profile.

Recommendations

To avoid this issue in the future, the following recommendations can be made:

Use the correct plugin file name: Ensure that the plugin file name is correct and does not contain any extra characters.
Use the correct plugin directory: Verify that the plugin file is placed in the correct directory.
Enable the plugin in the profile: Ensure that the plugin is enabled in the profile.
Update Lynis to the latest version: Verify that the Lynis version is up-to-date.

Future Development

In the future, it would be beneficial for the Lynis development team to address this issue and provide a solution to prevent Lynis from altering the phase2 plugin filename. This would ensure that users can use Lynis without encountering this issue.

Conclusion

Q: What is the issue with Lynis altering the phase2 plugin filename?

A: The issue with Lynis altering the phase2 plugin filename is that it adds "plugin" and "phase2" to the beginning and end of the file name, making it unable to be used.

Q: What are the symptoms of this issue?

A: The symptoms of this issue include Lynis being unable to read the plugin file correctly, and the plugin being skipped for phase 2.

Q: What are the troubleshooting steps to resolve this issue?

A: The troubleshooting steps to resolve this issue include:

Check the plugin file name: Ensure that the plugin file name is correct and does not contain any extra characters.
Check the plugin directory: Verify that the plugin file is placed in the correct directory.
Check the plugin profile: Ensure that the plugin is enabled in the profile.
Check the Lynis version: Verify that the Lynis version is up-to-date.

Q: What are the recommendations to avoid this issue in the future?

A: The recommendations to avoid this issue in the future include:

Use the correct plugin file name: Ensure that the plugin file name is correct and does not contain any extra characters.
Use the correct plugin directory: Verify that the plugin file is placed in the correct directory.
Enable the plugin in the profile: Ensure that the plugin is enabled in the profile.
Update Lynis to the latest version: Verify that the Lynis version is up-to-date.

Q: Is this issue specific to a particular plugin or Lynis version?

A: This issue is not specific to a particular plugin, but rather a general problem with the way Lynis handles phase2 plugin filenames. The issue was encountered on Lynis version 3.1.4.

Q: What is the expected behavior of Lynis in this scenario?

A: The expected behavior of Lynis is to read the custom plugin file provided in the appropriate directory mentioned in the documentation.

Q: What are the possible causes of this issue?

A: The possible causes of this issue include:

Incorrect plugin file name: The plugin file name may be incorrect or contain extra characters.
Incorrect plugin directory: The plugin file may be placed in the incorrect directory.
Incorrect plugin profile: The plugin may not be enabled in the profile.
Outdated Lynis version: The Lynis version may be outdated.

Q: How can I report this issue to the Lynis development team?

A: You can report this issue to the Lynis development team by submitting a bug report on the Lynis website or by contacting the development team directly.

Q: What is the current status of this issue?

A: The current status of this issue is that it is being investigated by the Lynis development team. A solution is being worked on to prevent Lynis from altering the phase2 plugin filename.