request to remove security=share
Christopher R. Hertel
crh at ubiqx.mn.org
Sun Mar 12 22:29:20 GMT 2006
> Why don't just add a read only password and a read write password ?
All of the systems that Samba currently uses to keep track of passwords
(or password hashes) are based on having a username as a starting point.
It makes sense to create a "special" user so that we can store the hashes
in the usual places. In addition, the underlying OS and FS want to have
valid user IDs and group IDs, so those have to be provided somehow.
So, basically, if you added a read only password and a read/write
password... where would you put them and how would you find them?
There are a lot of good answers to that question, but I think Volker is
looking for the simplest and least impacting.
> We already have the username option, we just need to change it to be
> the name of the user we are going to access the share with in the
> security=share case.
> For these shares the read only flag will be triggered based on the
> password used. Passwords will be stored in secrets.tdb indexed by
> This is an easy setup and follows what win9x has always done so that it
> makes more understandable to admins.
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/ -)----- crh at ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/ -)----- crh at ubiqx.org
More information about the samba-technical