Samba Share is Locked Down

Connection sharing, Firewall, Samba..etc
Forum rules
Before you post please read how to get help
Post Reply
StevenC21
Level 2
Level 2
Posts: 88
Joined: Mon Mar 19, 2018 11:02 pm

Samba Share is Locked Down

Post by StevenC21 » Thu Aug 02, 2018 6:34 pm

Hey everyone. I have a fairly major issue. Basically, I have a Samba Share running on a Raspberry Pi. That part is fine, my Linux Mint PC can see it and access the files, but it doesn't have write access, which is a fairly major issue. The entire share is read-only. Is there a way to fix this?

Here is the /etc/fstab entry:

Code: Select all

//192.168.42.130/share     /media/samba    cifs  credentials=/etc/samba/user.cred 0 0
Thank you for your time.

/etc/samba/smb.conf:

Code: Select all

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# 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 most of which 
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# 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]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# 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

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

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

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set 
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# 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
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

[homes]
   comment = Home Directories
   browseable = yes

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = no

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0775

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0775

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = yes
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

[share]
Comment = Pi shared folder
Path = /share
Browseable = yes
Writeable = Yes
only guest = no
read only = no
create mask = 0777
directory mask = 0777
Public = yes
Guest ok = yes
smb.conf but only [share]:

Code: Select all

Comment = Pi shared folder
Path = /share
Browseable = yes
Writeable = Yes
only guest = no
read only = no
create mask = 0777
directory mask = 0777
Public = yes
Guest ok = yes
Last edited by StevenC21 on Fri Aug 03, 2018 12:53 am, edited 1 time in total.
"A computer is like air conditioning. It becomes useless when you open Windows."
- Linus Torvalds

StevenC21
Level 2
Level 2
Posts: 88
Joined: Mon Mar 19, 2018 11:02 pm

Re: Samba Share is Locked Down

Post by StevenC21 » Thu Aug 02, 2018 11:56 pm

Bump.
"A computer is like air conditioning. It becomes useless when you open Windows."
- Linus Torvalds

ugly
Level 3
Level 3
Posts: 161
Joined: Thu Nov 24, 2016 9:17 pm

Re: Samba Share is Locked Down

Post by ugly » Fri Aug 03, 2018 12:31 am

I think the file that you need to provide is: /etc/samba/smb.conf

You probably need to add something like:

Code: Select all

read only = no
writable = yes
to your share.

StevenC21
Level 2
Level 2
Posts: 88
Joined: Mon Mar 19, 2018 11:02 pm

Re: Samba Share is Locked Down

Post by StevenC21 » Fri Aug 03, 2018 12:51 am

Alright, editted top post. Also, how should I go about testing to see if a solution worked?
"A computer is like air conditioning. It becomes useless when you open Windows."
- Linus Torvalds

altair4
Level 19
Level 19
Posts: 9186
Joined: Tue Feb 03, 2009 10:27 am

Re: Samba Share is Locked Down

Post by altair4 » Fri Aug 03, 2018 6:34 am

You have 1 possibly 2 issues:

On the server:
In order to have write access to guests you have to make sure the Linux permissions of the folder being shared allow it:

Code: Select all

sudo chmod 777 /share
On the Mint client:
Change this:
//192.168.42.130/share /media/samba cifs credentials=/etc/samba/user.cred 0 0
To this:
//192.168.42.130/share /media/samba cifs credentials=/etc/samba/user.cred,uid=1000,nounix 0 0
The uid=1000 changes ownership of the mounted share from root ( which right now is the only one who has write access ) to you. Just make sure 1000 is you by running this command and changing the fstab entry to match your uid number:

Code: Select all

id
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

StevenC21
Level 2
Level 2
Posts: 88
Joined: Mon Mar 19, 2018 11:02 pm

Re: Samba Share is Locked Down

Post by StevenC21 » Fri Aug 03, 2018 12:40 pm

Thanks man! But I must ask. What exactly does "nounix" do?

Edit: How will I test to see if it worked though? Should I reboot? Because I tried

Code: Select all

sudo mount -a
and it still is locked down.
"A computer is like air conditioning. It becomes useless when you open Windows."
- Linus Torvalds

altair4
Level 19
Level 19
Posts: 9186
Joined: Tue Feb 03, 2009 10:27 am

Re: Samba Share is Locked Down

Post by altair4 » Fri Aug 03, 2018 1:24 pm

sudo mount -a will mount things that are not already mounted so:

Unmount the share:

Code: Select all

sudo umount /media/samba
Remount with:

Code: Select all

sudo mount -a
Please add a [SOLVED] at the end of your original subject header if your question has been answered and solved.

StevenC21
Level 2
Level 2
Posts: 88
Joined: Mon Mar 19, 2018 11:02 pm

Re: Samba Share is Locked Down [Solved]

Post by StevenC21 » Fri Aug 03, 2018 3:30 pm

Thanks so much! That solved it!
"A computer is like air conditioning. It becomes useless when you open Windows."
- Linus Torvalds

Post Reply

Return to “Other networking topics”