A bug maybe; Write list access to Read only share; security = share?

[Tony Gaddis]

Thank you for the 'map to guest = bad user' tip.  That works like a charm in
'security = user' mode.

I can understand your position with respect to 'security = share'.  I will
use it to achieve what I need.

I am not sure that I know enough, but if there was anyway to contribute to
documenting the behaviors, I would be happy to help.

Again, given the complexities of MS file sharing, I find Samba an amazing
program.

Thanks
Tony Gaddis

-----Original Message-----
From: Gerald (Jerry) Carter [mailto:jerry at samba.org]
Sent: Wednesday, February 02, 2005 1:11 PM
To: Tony Gaddis
Cc: samba-technical at lists.samba.org
Subject: Re: A bug maybe; Write list access to Read only share; security
= share?


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wed, 2 Feb 2005, Tony Gaddis wrote:

> I posted this question on the samba list and after some discussion and
> several more trials, I think I have a bug in either the documenation or
> in the functionality.  Before posting the bug I wanted to post to the
> technical list, to make sure.
>
> I am running Samba 3.0.4 on a linux 2.4.26 kernel.
>
> I am using "security = share".  I want to present three shares to the
> users, Share - public read/write, Content - public read/controlled write
> list and Secure - controlled read/write. Listed at the message end are
> the relevant parts of my smb.conf.

My position on this is that it is too much to expect user level access
control to resources in security = share.  If you want to control access
based on user access, then my recommendation is to use 'security = user'
(as someone else mentioned).  I don't have any plans to change this
behavior in Samba3.

> When I posted to the samba list, I got a response about how someone was
> successful with security = user. When I tried that, a valid user (in
> smbpasswd file) had the expected access. However, a "guest" user (not in
> smbpasswd file) was prompted for a username/password for access to any
> share. They were not granted access as guest.

Did you set 'map to guest = bad user' ?





cheers, jerry
=====================================================================
Alleviating the pain of Windows(tm)      ------- http://www.samba.org
GnuPG Key                ----- http://www.plainjoe.org/gpg_public.asc
"I never saved anything for the swim back."     Ethan Hawk in Gattaca
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQFCAUHkIR7qMdg1EfYRAtFLAJ9R0T1DiGQXXvGP+S6fjrNqLRbZsQCgwAdL
XckTIrjf5lNmpviFoxfamQA=
=sOkg
-----END PGP SIGNATURE-----