4.1.0 group problem

[Onemangang]

Hi.

In my setup I am running it with several groups. And
when a new user is added, he should not be part of
any group. This mean he should only have access to
"/home". (all my users have a home dir.)

But when upgrading to the new version 4.1 i encountered
a funny thing. When using "site adduser name pass *@*"
it always adds the user to the "ioFTPD" group, not the
default group as expected.

I tried adding "groups" in the default.user profile but
it doesnt matter. I tried to make new admins group and
remove ioFTPD group, then it gets the admin group.
I changed the order in wich the groups are listed in
etc/group to make sure its not because it was first group
listet, still gets the "admins" group.

Ok, checking it all out i thought maybe its because it picks
the group with the lowest number in the etc/group file.

I changed my admins group to be 5000 and other groups as
1000 2000 3000 4000, and renamed the group files.
It still gets the admins group.

I havent found anywhere to set the default group but in the
default.user file. But it is ignored/not working.

But maybe I am doing something wrong?

Each time i made a change, the program was terminated,
change applied and then restartet t to make shure that
the new settings where applied.

Keep up the good work.

[Zer0Racer]

adduser always defaults to your primary group. if you want to add a user to a specific group use gadduser:
SITE GADDUSER <group> <user> <pass> <ident@ip>

Adding group to your Default.User will not work.

[-=DoBBeR=-]

this is not the way it works in neither gl nor raiden.
when user is added in gl using site adduser they are added to group nogroup, in raiden they are not added to any group

[darkone]

This is how it works in io

[-=DoBBeR=-]

not here, if I add a user with adduser they get added to grp siteop, just as the creator of this thread said..

crap =) I didnt read your reply properly, I dont want io to work this way =) it's really dangerous since I have a few ppl on my site that are siteops, if they by misstake use the very common site adduser instead of site gadduser they will put the user in grp siteop instead of nogroup, which at least I feel it should be..

[-=DoBBeR=-]

I think it would be alot safer to add users to nogroup than the group that the one who creates the account is in, and if the creator happens to be a user with the G flag, the user he creates could be the grp he's in..

[darkone]

Flag 'G' has no special meaning anymore in 4.1.0.. user with flag 'G' and without admingroups set, has permission to delete anyone or to add user in any group.
By saying 'this it how it works in io', I meant that it's intended behaviour that user is auto chgroupped to primary group of admin.

[-=DoBBeR=-]

ok, lets say that I'm masteruser and in primary group siteop, the only possible way for me to add a user to a group other than my own primary one, is to do site gadduser? and is this they way you are always going to have it? and finally, is there no way of making the default group for a new user "nogroup"?

tnx for your quick answers btw =)

[darkone]

I can't see why anyone would like to create users in NoGroup.. You'll save yourself from extra work by asking user to give group in his 'addline' & using gadduser.

[-=DoBBeR=-]

Sure, but ppl always make misstakes, even siteops, and since most siteops I know are used to the site adduser command, both on *nix platforms and in win, I just felt it would be safer if there was an option somewhere to make new users go into nogroup.

[darkone]

Don't give admin group any special priviledges.. use flags That's how most people do it in gl...

[-=DoBBeR=-]

ok, can I make it possible for siteops with a certain flag to view all the private dirs, cause I want all siteops to have axx to predirs etc

this is how I set it up now

Private = /+PRE/somegroup/ =siteop -user
Private = /+PRE/someothergroup/ =siteop -anotheruser

Is this possible with a flag?
I've tried flags 1V on siteops, but that didnt make it possible for them to view the dirs, and I sure as hell wont give them M =)

[Unique]

Dobber exactly what im asking myself.
That default adduser to own grp is kinda gay, since siteops r only ones able to add and all users would end up in siteop having xs to system files etc etc.

Secondly it would be great indeed to have flags with the vfs.
So i can only give masters xs to /system for instance, no matter what grp they r in.

Last real irritating thing is the deldir rights.. even a +1 guy cant del other peoples dirs..
You need to give them +V or +M to be able to del other peeps dirs.. not quite handy for a nuker..
Since this deldir fiasco i cant even set up a pre dir good, since grp members arent able to delete dirs from other members..
All in all i think raidens file system was way more logical.. (soz )
"Execute" in chmod for del rights was ****ing handy, and new files being same chmod as parent dir when set in a vfs also.
So easy to set up "group" dirs in matter of seconds.. in io i cant even get it after 20 mins looking :S (im dumb i guess)