To add to Jason's suggestion, create a username map with a user(i.e. smbuser) that has access to the share ONLY. chown someuser(NOT root):smbuser. Then set it chmod 775.
In the smb.conf: In the [Globals] add: username map = /path/to/username.map map to guest = bad user security = server (as per Jason) In the [Share] add: write list = smbuser guest ok = yes read only = no (as per Jason) Next, create the username.map file and add the line: smbuser = guest Finally, restart the smb service This will secure your box from most of the samba hacks but still allow read/write access to the share. The biggest rule with Samba, keep the smb.conf file as simple as possible. K.I.S.S. is the best rule. HTH On Sat, 2004-02-21 at 13:17, Jason Tower wrote: > it sounds like you should be using share level security, not user. make > sure your smb.conf says 'security = share', make sure the shares you > defined are 'read only = no' and chown them to nobody or chmod them to > 777, either way should work. restart smbd/nmbd and the other network > hosts should have full access to them. > > On Saturday 21 February 2004 12:53, [EMAIL PROTECTED] wrote: > > I have googled this and come up with tons of "stuff", none of it > > completely clear or concise. I am trying to connect a XP Pro box to a > > Samba file share using "user" level security. The Samba server is not > > a domain controller. All I need it to do is serve up this share so > > that the > > XP box can read and write to it. I can see the samba box from the XP > > station but when I click on it I get an error. > > > > Could someone point me to a link where these challenges specific to > > XP have been documented? Also, some example smb.conf files would also > > be helpful. Thanks for all the help. > > > > -- > > Hugh -- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
