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

6.2.10 - Users must own their homedirs - potential issue with 'nobody' #207

Closed
Thulium-Drake opened this issue Jun 9, 2022 · 1 comment · Fixed by #208
Closed

6.2.10 - Users must own their homedirs - potential issue with 'nobody' #207

Thulium-Drake opened this issue Jun 9, 2022 · 1 comment · Fixed by #208
Labels
bug Something isn't working

Comments

@Thulium-Drake
Copy link
Contributor

Thulium-Drake commented Jun 9, 2022

Describe the Issue
Control 6.2.10 wants to ensure all users own their defined homedirectory and in order to shield system accounts from this there's a lower limit for the user's UID before it comes in effect.

However, the nobody user has a UID of 65534 and is considered 'interactive' by the task. And therefore it changes the owner of / to nobody:root.

Now I'm far from certain that is will be a problem for the normal system's functioning, but it feels wrong.

I'll whip up a PR in a min :)

Control(s) Affected
6.2.10

Environment (please complete the following information):
Role version 2.0.0 (tag)

Possible Solution
Exclude nobody from 6.2.10

@Thulium-Drake Thulium-Drake added the bug Something isn't working label Jun 9, 2022
@Thulium-Drake Thulium-Drake changed the title 6.2.11 - Users must own their homedirs - potential issue with 'nobody' 6.2.10 - Users must own their homedirs - potential issue with 'nobody' Jun 9, 2022
@uk-bolly
Copy link
Member

uk-bolly commented Jun 9, 2022

Thanks for this work really appreciate the quick turn around and PR.

Regards

uk-bolly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants