At https://manpages.ubuntu.com/manpages/latest/man5/smb.conf.5.html go towards the end of EXPLANATION OF EACH PARAMETER:

   writable

       This parameter is a synonym for writeable.

   writeable (S)

       Inverted synonym for read only.

       Default: writeable = no
Answer from FedKad on askubuntu.com
🌐
LinuxQuestions.org
linuxquestions.org › questions › linux-server-73 › what's-the-difference-between-read-only=no-and-writable=yes-in-samba-756930
What's the difference between read only=no and writable=yes in Samba?
September 22, 2009 - What's the difference between read only=no and writable=yes in Samba? I see some docs stating read only=no means writable, then at this point, what's
Discussions

backup - Create samba share with only write and no read permissions - Unix & Linux Stack Exchange
Use case I'm the only user. I have an ubuntu NAS with fulldisk encryption, and I'm trying to back up my own Windows machines to that. I want to have a USB stick that I can boot from to clone the Wi... More on unix.stackexchange.com
🌐 unix.stackexchange.com
Read-only and read-write Samba user possible ? - General Support - LibreELEC Forum
Hi, I use LE as a media server in the house, but I do not want every body in the family being able to delete one of my valuable media, even not by accident. So I have tried to set up samba with one read-only user (maybe "guest") and one read-write user… More on forum.libreelec.tv
🌐 forum.libreelec.tv
November 18, 2016
raspbian - Samba share is read-only despite settings - Raspberry Pi Stack Exchange
I am running Samba on my Raspberry Pi, and have configured the smb.conf file as such, which should just be the default version with the following appended: [media] comment = Media path = /mnt/raid1/media valid users = @media force group = media create mask = 0660 directory mask = 0771 browseable = yes writable = yes read only ... More on raspberrypi.stackexchange.com
🌐 raspberrypi.stackexchange.com
samba - Linux filesystem only readable, not writable via SMB - Unix & Linux Stack Exchange
How do I actually make the folder writeable, instead of just readable? I added on lines such as writable = yes, write list = user, and force directory mode = 0777 to my Samba configuration as shown above, but it didn't seem to have helped at all. More on unix.stackexchange.com
🌐 unix.stackexchange.com
July 3, 2021
🌐
Reddit
reddit.com › r/selfhosted › smb share only works in read-only
r/selfhosted on Reddit: SMB share only works in read-only
February 17, 2024 -

I am new to Linux and tried to make a Samba share, to access files on an external hard drive (ext4), mounted on my Linux system, from a mac and a PC. I followed the steps on Ubuntu's website, and I can navigate in the share, but only in read-only. I would like all my shares to work with read-write permissions to the designated users.

Here is my smb.conf file:

#
# 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]

create mask = 0644
directory mask = 0755

## Browsing/Identification ###

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

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

#### 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

# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
   logging = file

# 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 server" 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

   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 = classic
# primary domain controller', 'server role = classic 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 config * :              backend = tdb
;   idmap config * :              range   = 3000-7999
;   idmap config YOURDOMAINHERE : backend = tdb
;   idmap config YOURDOMAINHERE : range   = 100000-999999
;   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 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 =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# 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 = yes

# 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 = 0700

# 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 = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make 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 = no
   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

[MOVIES]
    comment = MOVIES
    path = /media/MOVIES
    read only = no
    browsable = yes
    valid users = admin, myusername
    write list = admin, myusername

[DATA]
    comment = DATA
    path = /media/DATA
    read only = no
    browsable = yes
    valid users = admin, myusername
    write list = admin, myusername

[PUBLIC]
    comment = PUBLIC
    path = /media/DATA/PUBLIC
    read only = no
    browsable = yes
    valid users = admin, myusername, public
    write list = admin, myusername, public

🌐
O'Reilly
oreilly.com › openbook › samba › book › ch06_02.html
[Chapter 6] 6.2 Controlling Access to Shares
Like the valid users and invalid users options, this pair of options specifies which users have read-only access to a writeable share and read-write access to a read-only share, respectively. The value of either options is a list of users. read list overrides any other Samba permissions granted - as well as Unix file permissions on the server system - to deny users write access.
🌐
Linuxtopia
linuxtopia.org › online_books › network_administration_guides › using_samba_book › ch04_05_06.html
Using Samba - 4.5.1.5 read only and writeable
The options read only and writeable (or write ok ) are really two ways of saying the same thing, but approached from opposite ends. For example, you can set either of the following options in the [global] section or in an individual share: · If either option is set as shown, data can be read ...
Top answer
1 of 2
1

I've done something similar, only difference was that one user could write-only without reading (or even listing directory), another user could only read.

/etc/samba/smb.conf

[write-only]
  comment = Write-only access without read
  path = /smbshare
  hosts allow = 172.17.10.10
  hosts deny = 0.0.0.0/0
  read only = no
  write list = smbwrite
  force user = smbwrite
  force group = smbread
  create mask = 0350
  directory mask = 0350
  force create mode = 0350
  force directory mode = 0350

Initial access rights on server side:

chmod -R 350 /smbshare
chown -R smbwrite:smbread /smbshare

Only drawback is that if you know the exact file name, you can list it.

The following part is for a reference:

[read-only]
  comment = Read-only access
  path = /smbshare
  read only = yes
  hosts allow = 172.17.10.20
  hosts deny = 0.0.0.0/0
  read list = @smbread

/etc/fstab entries on both clients:

smbwrite (172.17.10.10), local user "foo":

//172.17.10.1/write-only      /mnt/write      cifs    user=smbwrite,pass=s3kr1t,uid=foo,vers=3.0 0 0

smbread (172.17.10.20), local user "bar":

//172.17.10.1/read-only /mnt/read cifs user=smbread,pass=s3kr1t,uid=bar,vers=3.0 0 0
2 of 2
1

Mount points only support disabling write (readonly), but not disabling read. However you may can do most of it with file permissions. It will not be possible to stop a user from reading her own files, but you can stop her from reading other peoples files.

You will need:

  • Sticky bit, to stop users from removing each others files.
  • Turn off the read bits of the directory to stop others from reading
  • Set a default permission, to turn off the read bits of files to stop others from reading them.

How to

  chmod +t "«the directory»"
  setfacl -m "u::wx,g::wx,o:-" "«the directory»"
  setfacl -m "d:u::-,d:g::-,d:o:-" "«the directory»"

Warnings

This will not be easily used by users, consider giving some extra permissions. Or one directory per user.

I also don't think that this is the way to do backups. Set up a cron job to do backups every day. You may be using backups for revision control, consider using a revision control system. Sub-version (svn), is a good one for must users, and most file types. Mercurial is also good for programmers, and can be used for other file-types, but I would not recommend it for any non-mergeable files (such as MS-Office).

Find elsewhere
🌐
LibreELEC
forum.libreelec.tv › libreelec forum › help & support › general support
Read-only and read-write Samba user possible ? - General Support - LibreELEC Forum
November 18, 2016 - If not, see <http://www.gnu.org/licenses/>. ################################################################################ # samba.conf v4 (do not remove) # This configuration file allows you to customize the samba shares # available from your machine [global] server string = LibreELEC browseable = yes printable = no deadtime = 30 mangled names = no name resolve order = host bcast printcap name = /dev/null load printers = no encrypt passwords = true enable core files = no passdb backend = smbpasswd smb encrypt = disabled map to guest = Bad User guest account = root security = user username m
🌐
Samba
samba.org › samba › docs › using_samba › ch06.html
Chapter 6. The Samba Configuration File
The options read only and writable (also called writeable or write ok ) are really two ways of saying the same thing, but they are approached from opposite ends.
🌐
Linux-training
linux-training.be › networking › ch18.html
Chapter 18. a writable file server
[root@RHEL52 samba]# mkdir -p /srv/samba/writable [root@RHEL52 samba]# chmod 777 /srv/samba/writable/ There are two parameters to make a share writable. We can use read only or writable.
🌐
Narkive
linux.samba.narkive.com › bAcixxFO › samba-write-list-vs-read-list
[Samba] write list vs read list
If you make a share "read only" then it is read only by default, yet those on the "write list" will have write privileges. The less complicated, the easier to read and troubleshoot. Post by Luca Ferrari [LABORATORIO_SMB] comment = Cartella privata Laboratorio path = /mnt/samba/lab_smb browsable ...
🌐
Samba
samba.org › samba › docs › using_samba › ch09.html
Samba
Like the valid users and invalid users options, this pair of options specifies which users have read-only access to a writable share and read/write access to a read-only share, respectively. The value of either options is a list of users. The read list parameter overrides any other Samba permissions granted—as well as Unix file permissions on the server system—to deny users write access.
🌐
Linux-training
linux-training.be › storage › ch23.html
Chapter 23. samba securing shares
[authwrite] path = /srv/samba/authwrite comment = authenticated users only read only = no guest ok = no create mask = 600 directory mask = 555 inherit permissions = yes · 1. Create a writable share called sales, and a readonly share called budget.
🌐
Linux-training
linux-training.be › storage › ch19.html
Chapter 19. a read only file server
The other way (called user mode) ... The share is called pubread and the path is set to our newly created directory. Everyone is allowed access (guest ok = yes) and security is set to read only......