Distribution EOLE

• sur Scribe 2.7.1, le range n'est pas "bon"
  

  root@scribe:~# rgrep 'range' /etc/samba/smb.conf 
          idmap config *:range = 2000-2999
          idmap config DOMSCRIBE:range = 10000-999999
  

• sur Scribe 2.7.1, il y a aussi du "nobody" qui traîne
  

  root@scribe:~# rgrep nobody /etc/samba/smb.conf 
          guest account = nobody
          invalid users = nobody guest
  

On pourrait conserver map to guest = Bad User mais, c'est peut-être la valeur par défaut (à vérifier)

• map to guest
  

                    ·   Never - Means user login requests with an invalid password are rejected. This is the default.
  
                    ·   Bad User - Means user logins with an invalid password are rejected, unless the username does not exist, in which case it is treated as a guest login and mapped into the guest account.
  
                    ·   Bad Password - Means user logins with an invalid password are treated as a guest login and mapped into the guest account. Note that this can cause problems as it means that any user
                        incorrectly typing their password will be silently logged on as "guest" - and will not know the reason they cannot access files they think they should - there will have been no
                        message given to them that they got their password wrong. Helpdesk services will hate you if you set the map to guest parameter this way :-).
  
                    ·   Bad Uid - Is only applicable when Samba is configured in some type of domain mode security (security = {domain|ads}) and means that user logins which are successfully authenticated
                        but which have no valid Unix user account (and smbd is unable to create one) should be mapped to the defined guest account. This was the default behavior of Samba 2.x releases. Note
                        that if a member server is running winbindd, this option should never be required because the nss_winbind library will export the Windows domain users and groups to the underlying OS
                        via the Name Service Switch interface.
  

Je propose également de supprimer la variable présentée comme suit dans la doc

Activer le mode invité sur le partage

Certaines configurations ou logiciels (exemple : WPKG) nécessitent de paramétrer des partages en mode invité (guest ok = yes).

Cela n'est possible que si le mode invité a été activé à l'aide de l'option Activer le mode invité sur le partage.

Les commits sont bien présents et la doc modifiée.