Samba et la conversion SID

Jtomoise · Le 13/03/2025, à 16:32

Bonjour
Je n'arrive pas à réaliser un partage de dossier avec Samba sur une machine version 24.04.2 LTS . Motif a priori :

« net usershare » a retourné l'erreur 255 : net usershare add: cannot convert name "Everyone" to a SID. {Access Denied} A process has requested access to an object but has not been granted those access rights.

alors que sur une autre machine 24.04 LTS (non encore mise à niveau), le problème ne se pose pas et le répertoire /var/lib/samba/usershares est complété comme il se doit.
En substance, comment permettre que la conversion SID soit réalisée ?
Cordialement

LRDP · Le 18/03/2025, à 22:09

Bonsoir,
peux-tu donner le retour de

cat /etc/samba/smb.conf

Jtomoise · Le 19/03/2025, à 10:24

Un gros point sensible ce smb.conf, probablement inutilement exhaustif pour ce qui me concerne et surtout au final d'une instabilité difficile à maîtriser. J'en suis conscient.
En résumé : Difficile au final de savoir "qui fait quoi"....
Mon objectif est de pouvoir partager des dossiers et fichiers entre mes deux ou trois machines (Ubuntu bien sûr) mais aussi accessoirement avec les laptops sous WIN$ (parce que personne n'est parfait ) de visiteurs occasionnels.
Perso NFS me convient parfaitement...
Cordialement

cat /etc/samba/smb.conf
#
# 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

   create mode = 664
   security = user
   
   workgroup = WORKGROUP 
   valid users = @sambashare
   read list = @sambashare
   write list = @sambashare
   netbios name = tom-HI81M-2DV
   
   usershare path = /var/lib/samba/usershares/   
   usershare max shares = 100
# server string is the equivalent of the NT Description field
   server string = SambaServer

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

    client min protocol = NT1                                                                                   

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

[shared] 
    path = /srv/samba/shared
    browsable = yes
    guest ok = yes
    read only = no
    create mask = 0775
    
   
# 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 = 0755


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

# 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


[sambashare]
    comment = Samba on Ubuntu
    path = home/%U/sambashare
    read only = no
    browsable = yes

LRDP · Le 19/03/2025, à 12:18

Bonjour
le dossier à partager est /sambashare ? et doit être disponible pour d'autres machines invitées ?
J'écrirais le /smb.conf ainsi :

[sambashare]
    comment = Samba on Ubuntu
    path = home/%U/sambashare
    read only = no
    browsable = yes
    guest ok = yes
    public = yes
    force user = #nom de l'utilisateur Ubuntu
    create mask = 0775
    directory mask = 0775

Ainsi ce dossier sambashare devrait être partagé correctement dans le réseau local, à priori même sans mot de passe (ce qui évite l'usage du mot de passe utilisateur par un invité), mais il faut que le contenu ne soit pas "sensible".
cette ligne : "include = /home/samba/etc/smb.conf.%m" est bizarre car samba est dans /etc et non dans /home quand on installe Samba.
Il n'est pas nécessaire d'être "serveur" pour partager des dossiers et fichiers à partir d'une seule machine, avec Samba.
Samba est critiqué par la plupart des utilisateurs Linux, pour ses défauts de sécurité. La preuve est mon conseil de modifier smb.conf pour rendre le partage accessible à tous, sans mot de passe. Mais si on a un réseau local sûr, utilisé par des personnes sûres, qui comportent des machines différentes (j'ai plusieurs postes Linux, Mac, Windows, Android, Apple) et Samba a toujours été pour moi facile d'emploi.
NFS est certainement plus sûr, plus "smart" mais un lecteur multimédia réseau ou certaines Box ne peuvent pas chercher des musiques sur un poste Linux, à moins d'entrer dans la configuration de l'appareil pour y installer une Api réseau.
Bon courage !

Jtomoise · Le 19/03/2025, à 13:01

Merci beaucoup
Je vais modifier ce partage [sambashare] créé de toute façon à titre expérimental.

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 13/03/2025, à 16:32

Samba et la conversion SID

#2 Le 18/03/2025, à 22:09

Re : Samba et la conversion SID

#3 Le 19/03/2025, à 10:24

Re : Samba et la conversion SID

#4 Le 19/03/2025, à 12:18

Re : Samba et la conversion SID

#5 Le 19/03/2025, à 13:01

Re : Samba et la conversion SID

Pied de page des forums