samba - May 2004 - write list bug reports [was Re: OTHER BUG IN SAMBA 3.0.4?! FORCE USE

> Hi jerry, and hi everyone !!!
> I've seen the bug 1319 has appeared...
> (Remember I previously applied the 1315 ?)
> Has this one something to do with ADS domain member and winbind 
> authentification for shares ?
My Samba 3.0.4 server is an W2k3 ADS domain member, it uses winbind and 
kerberos as authentication for shares, so "security = ADS". 

I have the same problem (bug 1319) on my print$ share (Printer Driver Upload 
share) for CUPS printers. After upgrading to 3.0.4 I couldn't upload printer
drivers
anymore, I received the following message when I used the APW for installing a
new
driver: "Printer xxxxx not installed; access denied" (or a message
like that).
My print$ share looks like this:
 
[print$]
comment = Printer Driver Download Area
path = /etc/samba/drivers
write list = root, '@TEST.COM\Domain Admins', 
@TEST.COM\DEP_ADMIN_GERMANY
force user = root
guest ok = Yes 

This means this share is standard in "read-only" mode and it uses the
"write list" for
write access. 

I had to add "read only = No" to the print$ share, so I could upload
printer drivers.
For now I can use "read only = No" if I have to upload printer drivers
and "read only =
Yes" when I'm finished, but it is just a workaround... 

Regards, 
Alex.

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

Alex de Vaal wrote:

| I have the same problem (bug 1319) on my print$ share
| (Printer Driver Upload  share) for CUPS printers. After upgrading
| to 3.0.4 I couldn't upload printer drivers anymore, I received
| the following message when I used the APW for installing a new
| driver: "Printer xxxxx not installed; access denied" (or a
| message like that).  My print$ share looks like this:
|
| [print$]
| comment = Printer Driver Download Area
| path = /etc/samba/drivers
| write list = root, '@TEST.COM\Domain Admins',
| @TEST.COM\DEP_ADMIN_GERMANY
| force user = root
^^^^^^^^^^^^^^^^^^^
| guest ok = Yes
|
| This means this share is standard in "read-only" mode and it uses
| the "write list" for  write access.

please see the patch attached to bug 1319 (as of yesterday) and
try it out.  The bug is actually an interaction between
'force user' adn 'write list'





cheers, jerry
- ----------------------------------------------------------------------
Hewlett-Packard            ------------------------- http://www.hp.com
SAMBA Team                 ---------------------- http://www.samba.org
GnuPG Key                  ---- http://www.plainjoe.org/gpg_public.asc
"...a hundred billion castaways looking for a home." ----------- Sting
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAqiuRIR7qMdg1EfYRAvMHAJ0ZumjHTLMSUAYCWNQe2y5RGHreWwCgneyK
5yt6qgMHS2xtORuhiyhQu/8=ZiQJ
-----END PGP SIGNATURE-----

On Tue, May 18, 2004 at 05:20:59PM +0200, Alex de Vaal
wrote:
> [print$]
> comment = Printer Driver Download Area
> path = /etc/samba/drivers
> write list = root, '@TEST.COM\Domain Admins', 
> @TEST.COM\DEP_ADMIN_GERMANY
> force user = root
> guest ok = Yes 
On a related note, what's the point of having every user connected as
root and also use a write list, specially for other users besides root?
What is the expected behaviour here? Wouldn't it be best to use "valid
users" instead of the write list? I'm a little confused about this
scenario.

What takes precedence, force user or write list?

On 18 May 2004 at 10:28, Gerald (Jerry) Carter wrote:
> please see the patch attached to bug 1319 (as of yesterday) and
> try it out.  The bug is actually an interaction between
> 'force user' adn 'write list'
Sorry for the late answer.

Can you tell me how to apply this patch (or tell me where I can find the 
documentation how to do it)? 
I always compile Samba from the source RPMS (of RHL9) on the Samba FTP site 
on my RHL9 Linux server (don't know how to do it else... ;-).

Cheers,
Alex.