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.combackup - Create samba share with only write and no read permissions - Unix & Linux Stack Exchange
Read-only and read-write Samba user possible ? - General Support - LibreELEC Forum
raspbian - Samba share is read-only despite settings - Raspberry Pi Stack Exchange
samba - Linux filesystem only readable, not writable via SMB - Unix & Linux Stack Exchange
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
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
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).
We need more info as to how the shares are set up. A printout of the share definitions would help. Are you using ACL's or defining the share permissions from within the share definition? What do you mean by "setting the read only flag"? You mean right clicking on the file and checking the Read Only box? If so, that's not the best way to go, and you should look into implementing ACL's. Windows XP's filesystem is heavily dependent on them, and SAMBA can work with them perfectly.
If you don't want to force everyone to connect as the same user, you can force the correct group membership using the string: "force group". What tends to throw people off is that the user may already be a member of the local Linux group, but as far as SMB is concerned, the group you 'connect as' from Windows is what matters here.
EXAMPLE:
[someshares]
path=/path/to/someshares
writable = yes
browsable = yes
valid users = @somegroup
create mask = 0775
force create mode = 0775
directory mask = 0775
**force group = somegroup**
read only = no
read only = yes
The documentation is your friend.
This happens because you have:
browseable = yes
change it to:
browseable = no
It`s tricky, but now you won't see the the folder in the browser, but you can put the full address in the address bar of the file explorer and access to it :
\\\ip_or_name_of_the_computer\shared_Folder
and you can read to the files with readonly access (only read, not delete or create new file )
if you need to access from the command prompt in Windows you can do it the same way:
\\ip\shared_folder\file
or with net use :
net use s: \\ip\shared_folder
and access it changing the drive to s:
The problem is the config line:
vfs objects = catia fruit recycle streams_xattr
Note the requirements of the VFS module streams_xattr:
The file system that is shared with this module enabled must support xattrs.
After removing streams_xattr at least writing once worked. However deleting and writing again made problems. Removing fruit alltogether, although using samba only from a mac client, made file operations work as expected.
I am also using dperson/samba with a exFAT mount, and was having similar issues with a Windows 10 client giving this error whenever I tried to rename/move/delete (but creating files worked)
Error 0x80070032: The request is not supported.
as you said, the fix was to remove fruit and streams_xattr from vfs objects line in /etc/samba/smb.conf
vfs objects = catia recycle
$ docker exec -it samba bash
$ vi /etc/samba/smb.conf
# in vi, delete fruit and streams_xattr from vfs objects =
$ exit
$ docker restart samba
Edit /etc/samba/smb.conf
# command line
sudo -e /etc/samba/smb.conf
# graphical
gksu gedit /etc/samba/smb.conf
Add in the write list paramter to your share definition, add in your list of users allowed write access.
write list = user1 user2 user3
You can use read list as well
read list = guest, nobody
So ...
[share]
comment = Ubuntu Share
path = /your/samba/share
browsable = yes
guest ok = yes
read only = yes
write list = user1 user2 user3
create mask = 0755
If you need finer grain of control, you can use acl (access control lists) on the server.
Read only parameter is a Boolean value, so this should be more like one of the following:
[share]
comment = Ubuntu Share
path = /your/samba/share
browsable = yes
guest ok = yes
read only = no
read list = guest nobody
write list = user1 user2 user3
create mask = 0755
[share]
comment = Ubuntu Share
path = /your/samba/share
browsable = yes
guest ok = yes
read only = yes
write list = user1 user2 user3
create mask = 0755