[Bugs] [Bug 1775637] New: Remove guest access by default for GlusterFS volume SMB shares added by hook scripts

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1775637

            Bug ID: 1775637
           Summary: Remove guest access by default for GlusterFS volume
                    SMB shares added by hook scripts
           Product: Red Hat Gluster Storage
           Version: rhgs-3.5
          Hardware: x86_64
                OS: Linux
            Status: NEW
         Component: samba
          Severity: medium
          Assignee: gdeschner at redhat.com
          Reporter: anoopcs at redhat.com
        QA Contact: vdas at redhat.com
                CC: bugs at gluster.org, rhs-smb at redhat.com
        Depends On: 1775612
  Target Milestone: ---
    Classification: Red Hat



+++ This bug was initially created as a clone of Bug #1775612 +++

Description of problem:
SMB share section for GlusterFS volume added by Samba hook scripts with the
help of user.smb/user.cifs volume set option currently has the following
format:

[gluster-$VOLNAME]
comment = For samba share of volume $VOLNAME
vfs objects = glusterfs
glusterfs:volume = $VOLNAME
glusterfs:logfile = $LOGFILEBASE/glusterfs-$VOLNAME.%M.log
glusterfs:loglevel = 7
path = /
read only = no
guest ok = yes
kernel share modes = no

Allowing guest access with "guest ok = yes" is not a basic requirement and is
purely an optional share parameter. Furthermore it could lead SMB client to
attempt SMB requests out of a guest session resulting in minor issues from
different use cases.

Version-Release number of selected component (if applicable):
master

--- Additional comment from Worker Ant on 2019-11-22 17:41:26 IST ---

REVIEW: https://review.gluster.org/23745 (extras/hooks: Remove smb.conf
parameter allowing guest access) posted (#1) for review on master by Anoop C S


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1775612
[Bug 1775612] Remove guest access by default for GlusterFS volume SMB shares
added by hook scripts
-- 
You are receiving this mail because:
You are on the CC list for the bug.