Skip to content
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

Lynis error: permissions are not strict enough #55

Closed
nununo opened this issue Oct 19, 2020 · 2 comments
Closed

Lynis error: permissions are not strict enough #55

nununo opened this issue Oct 19, 2020 · 2 comments

Comments

@nununo
Copy link

nununo commented Oct 19, 2020

After installing Lynis in a Debian 10 using v4.0.0 I'm getting this error:

Fatal error: permissions of file /opt/lynis/db/languages/en are not strict enough. Access to 'owner' should be read-write, or read. Change with: chmod u=rw /opt/lynis/db/languages/en

Once I follow the suggestion I get:

Fatal error: permissions of file /opt/lynis/db/languages/en are not strict enough. Access to 'group' should be read-write, read, or none. Change with: chmod g=r /opt/lynis/db/languages/en

And once I follow this suggestion i get:

Fatal error: permissions of file /opt/lynis/include/parameters are not strict enough. Access to 'owner' should be read-write, or read. Change with: chmod u=rw /opt/lynis/include/parameters

Lynis documentation says this:

To protect alteration of the files, Lynis perform a few security checks. If the related files are not owned by root, or their
permissions are not strict enough, Lynis will show this on screen, including the commands to fix it. Usually it is caused because files were untarred by a user other than root.

Looking at install.yml it seems like in commit 4e08756 the untar file permissions where forced to 750 to comply with ansible-lint. But it seems like Lynis is not pleased unless it sees is files with 640.

And yet, changing the untar permissions from 750 to 640 will probably not suffice because I'm guessing that the actual executable probably still needs to be 750.

I hope this helps. Thanks in advance.

infothrill added a commit that referenced this issue Oct 19, 2020
@infothrill
Copy link
Owner

version 4.1.0 released, which fixes this

@nununo
Copy link
Author

nununo commented Oct 19, 2020

Wow! Thank you for such a quick reaction!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants