Arch Linux

risegeek

Member

From: /dev/null

Registered: 2011-02-15

Posts: 16

[SOLVED] Samba share problems

Hey guys,

So I've been trying to create an unauthorized set of samba shares, I've managed to allow a guest user to connect to the drives without authentication however files that I copy from outside the shares cannot be modified by my guest. Is it possible for me to allow guests to modify files that do not belong to them? my example is below;

cp /etc/motd /home/shares/downloads

ls -l
-rw-r--r-- 1 sam   users 406 Feb 16 02:29 motd
-rw-rw---- 1 guest users   0 Feb 16 02:37 test.txt

I attempt to modify the motd and it will not let me save apologies for any sheer stupidity, I'm still fairly new to this. Below is my smb.conf

# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options (perhaps too
# many!) most of which are not shown in this example
#
# For a step to step guide on installing, configuring and using samba, 
# read the Samba-HOWTO-Collection. This may be obtained from:
#  http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
#
# Many working examples of smb.conf files can be found in the 
# Samba-Guide which is generated daily and can be downloaded from: 
#  http://www.samba.org/samba/docs/Samba-Guide.pdf
#
# Any line which starts with a ; (semi-colon) or a # (hash) 
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
#
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors. 
#
#======================= Global Settings =====================================
[global]

# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = Server 1

# Security mode. Defines in which mode Samba will operate. Possible 
# values are share, user, server, domain and ads. Most people will want 
# user level security. See the Samba-HOWTO-Collection for details.
   security = user

# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
;   hosts allow = 192.168.1. 192.168.2. 127.

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   load printers = yes

# you may wish to override the location of the printcap file
;   printcap name = /etc/printcap

# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
;   printcap name = lpstat

# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
;   printing = cups

# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
  guest account = guest
  map to guest = Bad User

# this tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/%m.log

# Put a capping on the size of the log files (in Kb).
   max log size = 50

# Use password server option only with security = server
# The argument list may include:
#   password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
#   password server = *
;   password server = <NT-Server-Name>

# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
;   realm = MY_REALM

# Backend to store user information in. New installations should 
# use either tdbsam or ldapsam. smbpasswd is available for backwards 
# compatibility. tdbsam requires no further configuration.
   passdb backend = tdbsam

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting.
# Note: Consider carefully the location in the configuration file of
#       this line.  The included file is read at that point.
;   include = /usr/local/samba/lib/smb.conf.%m

# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
;   interfaces = 192.168.12.2/24 192.168.13.2/24 

# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
;   local master = no

# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
;   os level = 33

# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
;   domain master = yes 

# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
;   preferred master = yes

# Enable this if you want Samba to be a domain logon server for 
# Windows95 workstations. 
;   domain logons = yes

# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
;   logon script = %m.bat
# run a specific logon batch file per username
;   logon script = %U.bat

# Where to store roving profiles (only for Win95 and WinNT)
#        %L substitutes for this servers netbios name, %U is username
#        You must uncomment the [Profiles] share below
;   logon path = \\%L\Profiles\%U

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
;   wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
#    Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one    WINS Server on the network. The default is NO.
;   wins proxy = yes

# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
   dns proxy = no 

# These scripts are used on a domain controller or stand-alone 
# machine to add or delete corresponding unix accounts
;  add user script = /usr/sbin/useradd %u
;  add group script = /usr/sbin/groupadd %g
;  add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
;  delete user script = /usr/sbin/userdel %u
;  delete user from group script = /usr/sbin/deluser %u %g
;  delete group script = /usr/sbin/groupdel %g


#============================ Share Definitions ==============================
[Music]
path = /home/shares/music
public = yes
writable = yes
printable = no
read only = no
guest ok = yes
write list = @users
directory mask = 0777

[Pictures]
path = /home/shares/pictures
public = yes
writable = yes
printable = no
read only = no
guest ok = yes
write list = @users
directory mask = 0777

[Videos]
path = /home/shares/videos
public = yes
writable = yes
printable = no
read only = no
guest ok = yes
write list = @users
directory mask = 0777

[Downloads]
path = /home/shares/downloads
public = yes
writable = yes
guest ok = yes
create mask = 0660
write list = @users

[Back-ups]
path = /home/shares/backups
public = yes
writable = yes
printable = no
read only = no
guest ok = yes
write list = @users
directory mask = 0777

Last edited by risegeek (2011-02-17 01:47:12)

risegeek

Member

From: /dev/null

Registered: 2011-02-15

Posts: 16

Re: [SOLVED] Samba share problems

Hmm, been thinking this morning on my way to College I could always allow unauthenticated logins on the sam account like I am with the guest? this would solve my problem I guess. Unless of course anyone can shed some light on this and offer a better solution?

appreciate it guys take it easy!

eldragon

Member

From: Buenos Aires

Registered: 2008-11-18

Posts: 1,029

Re: [SOLVED] Samba share problems

check the permissions on the motd file.

the account in your system acting as the guest account has to have write permissions (aka, 644 = rw for owner and read for group and everyone else).

so, the guest account has to be sam, or the file has to be 664 instead.

you could add create mask and directory mask properties to your shares so that new files have the required permissions too.

risegeek

Member

From: /dev/null

Registered: 2011-02-15

Posts: 16

Re: [SOLVED] Samba share problems

Aye, I tried implementing the create mask & directory mask properties to a share - it was however to no avail, 'tis weird :S As soon as I head home I'll see how things are with the guest account being sam. Cheers dude.

risegeek

Member

From: /dev/null

Registered: 2011-02-15

Posts: 16

Re: [SOLVED] Samba share problems

Hmm, seems that the linux user account and the samba account passwords need to be identical for this to work? if I define no password for the samba account sam and if it has a password on the linux box itself, it will not work :S am I missing something?

Also might be worth taking note that if a conflict exists between the password then it also renders my other account such as guest inaccessible, I've got it back to working the way it was before

EDIT: I've managed to get this working, for some reason once I needed to remove the sam account that I created within smbpasswd - once I had done this I was able to use sam as the guest account? Samba is a little bit like pissing in the dark sometimes Ahh well.

Last edited by risegeek (2011-02-17 01:46:56)