Query regarding share-level security

[Marc Kaplan]

Rajan,

> share i specify the option "user = user3". The samba server has been
> restarted after the above changes in the config file.
> 
> Now, going by the definition of "share-level security", only user2
> should be allowed to access the share. But in my case, both user1 and
> user2 are able to access the share.
If you set user = user3, and user2 and user3 have the same password, then
shouldn't both user3 and user2 be able to access the share?

If user2 and user3 have the same password, then they will both be able to
connect to this share in share level security. When you have share level
security configured, the user you connect as doesn't actually matter at all.
The smb.conf parameter user = user3 simply says match the password the
client sends against the "share password". In this case the "share password"
is the password for user3. If you want user2 to be able to access this
share, but not user3 make the passwords differ, and ensure that user3
doesn't know user2's password.

If user1 has the same password as user2 and user3 then the same rule
applies.

			-Marc

> -----Original Message-----
> From: Rajan Aggarwal [mailto:rajan at amplewave.com]
> Sent: Tuesday, July 08, 2003 11:03 AM
> To: samba-technical at lists.samba.org
> Subject: Query regarding share-level security
> 
> 
> Hi All!
>     I am facing a problem for password protection at share level.
> 
> There are 2 users (user1 and user2) locally configured on my Linux
> machine. The Linux passwords for both have been configured and for
> simplicity the samba passwords for both are kept same as the 
> Linux ones.
> 
> Then , I created another user (user3) and assigned it the 
> same password
> as for user2. Then i edited the file...smb.conf wherein under 
> a specific
> share i specify the option "user = user3". The samba server has been
> restarted after the above changes in the config file.
> 
> Now, going by the definition of "share-level security", only user2
> should be allowed to access the share. But in my case, both user1 and
> user2 are able to access the share.
> 
> Does it indicate some problem with share-level security or is it some
> wrong configuration issue?
> 
> Regards,
> Rajan Aggarwal.
> 
> 
>