Topic: exclude from everyone (shared) group

[bunkobugsy]

Is there any way to exlcude a user from the shares accessible for the everyone (shared) group?

I'm not referring to the   db accounts setprop username EveryoneEmail no   email setting.

Thanks in advance, sorry if I didn't search long enough

[janet]

bunkobugsy

Is there any way to exclude a user from the shares accessible for the everyone (shared) group?

Don't use the shared group.
Create a new group & give the shares access rights via that group.
Add all users to that new group except the one user you want to exclude.

[bunkobugsy]

Thanks, had thought of this, it wouldn't work for write=group, read=everyone case.

Any other custom-template way to remove a user from the samba shared group?

[Stefano]

Thanks, had thought of this, it wouldn't work for write=group, read=everyone case.

as Janet said, create a group with all the users you need and give read and write right to that group, don't use everyone

[bunkobugsy]

What happens if I need to choose Write=group, Read=everyone scenario?

The only two other options are Write=admin, Read=group and Write=group, Read=group.

Everyone and admin are hardcoded and the only selectable variable is the group.

Isn't there way to custom-template the shared group?

Or is this achievable only with SharedFolders?

[Stefano]

well.. it seems like we have a X Y problem here..
you've got the solutions, but you're looking for something different

[bunkobugsy]

I'm looking for the easiest way, maybe I overlooked it somehow. Just asking...

[janet]

bunkobugsy

Thanks, had thought of this, it wouldn't work for write=group, read=everyone case.

I think you missed the point.

Use write=Group, read=Group
with only the users you want to have access, as members of that group.

[bunkobugsy]

Still in Write=group, Read=group scenario it's the same set of users,
whereas in Write=group, Read=everyone there're two different groups.

[janet]

bunkobugsy

You have to create another group (call it say alluser-1) that includes all users except the one user.
Whenever you add a new user to the system then you add them to the alluser-1 group by default.
Then everone group will match alluser-1 group (except for the one user).

Is that not uderstandable to you ?

[bunkobugsy]

Perfectly (from your first reply).

Don't mean to be rude, thanks all for helping, but:

what do I do when I need  Write=group, Read=everyone ?

There is no option to define Write=group1, Read=group2.

(Where group2 would be alluser-1, but it's hardcoded to everyone)

[Stefano]

Is there any way to exlcude a user from the shares accessible for the everyone (shared) group?

this is from your initial request.. you've the answer..

why do you need everyone group?

[Daniel B.]

Perfectly (from your first reply).

Don't mean to be rude, thanks all for helping, but:

what do I do when I need  Write=group, Read=everyone ?

There is no option to define Write=group1, Read=group2.

(Where group2 would be alluser-1, but it's hardcoded to everyone)

Ibays permissions model is limited. That's why I wrote the shared folders contrib. If you need finer ACL, I suggest you use shared foldes.

[bunkobugsy]

this is from your initial request.. you've the answer..

why do you need everyone group?

Because sometimes it is necessary for a group of people to publish something and everyone else to just view it.

[bunkobugsy]

Ibays permissions model is limited. That's why I wrote the shared folders contrib. If you need finer ACL, I suggest you use shared foldes.

And a big thank you for that