Remove writable group file due to issues with being able to give su access when shouldn't be allowed. #653
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change is to revert making the
/etc/group
file writable as part solution to avoid issues as discussed in #560.Although it means in environment where container run as group ID not in
/etc/groups
you will get a warning:in certain situations when creating an interactive shell in the container, there is no known Python packages or applications which will fail if running with a group ID not in
/etc/group
.With the
/etc/group
file once again not writable, as part of #560 can then work out whether restrictingsu
to members ofwheel
group can be done and lock downsu
for normal case.