On 07/10/2014 03:10 PM, Reindl Harald wrote:
Am 10.07.2014 16:59, schrieb Jóhann B. Guðmundsson:
>On 07/10/2014 12:51 PM, Zbigniew Je;drzejewski-Szmek wrote:
>>An administrator might want to block a certain sysusers config file from
>>being executed, e.g. to block the creation of a certain user.
>>---
>> src/sysusers/sysusers.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>>diff --git a/src/sysusers/sysusers.c b/src/sysusers/sysusers.c
>>index 129493a1e7..68c552d24a 100644
>>--- a/src/sysusers/sysusers.c
>>+++ b/src/sysusers/sysusers.c
>>@@ -62,6 +62,8 @@ typedef struct Item {
>> static char *arg_root = NULL;
>> static const char conf_file_dirs[] =
>>+ "/etc/sysusers.d\0"
>>+ "/run/sysusers.d\0"
>> "/usr/local/lib/sysusers.d\0"
>> "/usr/lib/sysusers.d\0"
>> #ifdef HAVE_SPLIT_USR
>
>How does this handle multiple users and if I as an administrator I wanted to
>block some users from being created I simply would not have installed the
>component that created him in the first place no?
you sound like it is always clear what package, probably installed as
dependency creates a user before - not speaking about that most packages
due uninstall don't remove the users created in rpm scripts
If you are an administrator you will quickly notice or do the necessary
research into what created the user that you dont want installed on your
system and take the necessary precaution from that happening again.
And arguable upstream should not be binding itself to solve downstream
distribution packaging problems be it rpm, be it deb or something else
since the installation scene is on the verge of changing...
JBG
_______________________________________________
systemd-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
