Bug 3333 - Uncorrect smb.conf in a subsection of Samba-3 HOWTO
Summary: Uncorrect smb.conf in a subsection of Samba-3 HOWTO
Status: CLOSED FIXED
Alias: None
Product: Samba Web
Classification: Unclassified
Component: content (show other bugs)
Version: current
Hardware: All Linux
: P3 major
Target Milestone: ---
Assignee: John H Terpstra (mail address dead(
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-15 07:57 UTC by Mike Sowka
Modified: 2005-12-20 06:52 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Sowka 2005-12-15 07:57:12 UTC
In Section I.2 under Worked Examples the subsection on Secure Read-Write File and Print Server has uncorrect permissions for the public share. According to the paragraph above the public drive should allow authenticated users only to store files, but:
...
[public]
comment = Data
path = /export
force user = maryo
force group = users
guest ok = Yes
read only = No
...
 allows anyone (i.e., guest) to write/delete files too.

I'm a newbie, so I don't know how to set this up correctly, such that guest only has read, and authenticated users have read/write. But for now I have remedied this example setup by adding 'valid users = bla, blue, ble' such that only they have access to the share at _all_.

Please address this in the docs so as not to mislead any other newbies like me... ;), and if You could suggest a way to have a share with read only for guest, and all access for valid users.

Thanks,
Mike
Comment 1 Deryck Hodge 2005-12-18 15:53:29 UTC
Passing to jht since this is docs related.
Comment 2 John H Terpstra (mail address dead( 2005-12-19 16:54:04 UTC
That was a booboo. Sorry.

I removed the "guest ok" parameter.

- John T.
Comment 3 Mike Sowka 2005-12-20 06:52:10 UTC
Second part of my bug report was a quick question ;) :

How do we setup a secure share that has _read_ _only_ for the guest?

Suggestions?
Mike

(In reply to comment #2)
> That was a booboo. Sorry.
> 
> I removed the "guest ok" parameter.
> 
> - John T.
>