But if you end up forced into it, look at Samba's "force user" and
"force
group" config settings. You might be able to get what you want with
those.
Possibly.. but opening up stuff for apache to write into. Users would
have to be in the apache group, so any user could just go into
another user
p dont think wrote:
But if you end up forced into it, look at Samba's "force user" and
"force
group" config settings. You might be able to get what you want with
those.
Possibly.. but opening up stuff for apache to write into. Users would
have to be in the apache group, so any user could just g
But if you end up forced into it, look at Samba's "force user" and "force
group" config settings. You might be able to get what you want with
those.
Possibly.. but opening up stuff for apache to write into. Users would
have to be in the apache group, so any user could just go into another
users
Dwight Tovey wrote:
FWIW: I think this is a REALLY bad idea. You will have all kinds of
issues with security, maintenance, ...
I agree.
But if you end up forced into it, look at Samba's "force user" and "force
group" config settings. You might be able to get what you want with
those.
Possibly.. b
certainly, especially if they create files or folders via samba and try
to access them thru SM, since surely samba won't create files w/group
ownership of apache
one solution is to run a daily (more often?) cron that blasts thru
users' home directories resetting the group on everything to apac
> it can work it does *not* need to be apache:apache, it can be
user:apache
>
... and then I'd have to put users in "apache" - hrm..
not necessarily, although it'll probably make it easier
>> The Boss thinks that internally, users can access their $HOME via
Samba, externally they can acces
Can it be used as a basic "home directory file" browser?
sure
Since stuff
will need to be owned by apache:apache, I guess that trying to use it in
such a manner wouldn't exactly work, eh?
it can work it does *not* need to be apache:apache, it can be
user:apache
The Boss thinks that intern
Can it be used as a basic "home directory file" browser? Since stuff
will need to be owned by apache:apache, I guess that trying to use it in
such a manner wouldn't exactly work, eh?
The Boss thinks that internally, users can access their $HOME via Samba,
externally they can access it via this
