-
Notifications
You must be signed in to change notification settings - Fork 93
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
roles: hosted_engine_setup: Adjust files permissions #409
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, although I wonder if we shouldn't try to use 770 or 660 masks
I personally think that 0770/0660 are mandatory, and if they do not work, we should find out why and fix that. The image includes sensitive stuff (hashed root password) and might include other sensitive stuff from user customization. |
roles/hosted_engine_setup/tasks/bootstrap_local_vm/02_create_local_vm.yml
Outdated
Show resolved
Hide resolved
roles/hosted_engine_setup/tasks/bootstrap_local_vm/02_create_local_vm.yml
Outdated
Show resolved
Hide resolved
roles/hosted_engine_setup/tasks/bootstrap_local_vm/02_create_local_vm.yml
Outdated
Show resolved
Hide resolved
roles/hosted_engine_setup/tasks/create_target_vm/03_hosted_engine_final_tasks.yml
Outdated
Show resolved
Hide resolved
Verified and opened https://bugzilla.redhat.com/show_bug.cgi?id=2035631 |
Adjusting files permissions for supporting umask 077 Bug-Url: https://bugzilla.redhat.com/2020620 Signed-off-by: Asaf Rachmani <arachman@redhat.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks fine to me. Perhaps worth documenting our considerations in the commit message or in comments.
Adjusting files permissions for supporting umask 077.
For security purposes we decided to use 770/660 permissions for the localvm directory, this directory contains the appliance image, and for creating the engine VM we must have its user/group configured for
qemu
, otherwiseqemu
user won't have search permissions for the appliance image (see also https://libvirt.org/drvqemu.html#posix-users-groups).Therefore we have decided to use
qemu
group instead ofkvm
.Bug-Url: https://bugzilla.redhat.com/2020620
Signed-off-by: Asaf Rachmani arachman@redhat.com