-
Notifications
You must be signed in to change notification settings - Fork 4
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
Refacto user group #69
base: master
Are you sure you want to change the base?
Conversation
- remove group steamengine_app_user - add user steamengine_app_user to group steamengine_project_user - update steamengine binary to be owned by steamengine_project_user and review permission accordingly - update steamengine_app_user and other extra users (apache, nginx, ...) to be member of group steamengine_project_user
group: "{{ steamengine_project_user }}" | ||
mode: 0750 |
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.
Juste read et execute pour l'owner ?
Le groupe n'en a pas besoin ? (question pour savoir)
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.
Ah ok je pense avoir compris why
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.
Yep le donner au group c'est permettre aux utilisateurs applicatif de l'utiliser
Du coup je retire l'owner du root qui dans tout les cas à les droits et je donne les droits à l'utilisateur projet seulement et non applicatif dessus en read/execute
Avant il n'y avait que l'utilisateur projet dans ce groupe donc ça ne posait pas de problème
32f935e
to
0dca2de
Compare
En draft le temps de vérifier à l'utilisation sur GU |
d5f0bb2
to
cff6be1
Compare
No description provided.