Bug 763769 (GLUSTER-2037) - 3.1.1-QA4: CIFS access is not being configured correctly
Summary: 3.1.1-QA4: CIFS access is not being configured correctly
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-2037
Product: GlusterSP
Classification: Retired
Component: core
Version: 3.1.0
Hardware: All
OS: Windows
urgent
medium
Target Milestone: 3.1.2
Assignee: Balamurugan Arumugam
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-28 17:58 UTC by Jacob Shucart
Modified: 2011-02-10 12:42 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jacob Shucart 2010-10-28 17:58:08 UTC 
If I create some users and then add CIFS access restricted to those users, I am still able to connect to the CIFS share with read-only access and I can copy files out of the share.  Write access is restricted as it should be, but both of them should be disabled if we are restricting access.
Comment 1 Balamurugan Arumugam 2010-10-29 05:56:12 UTC 
We are not able to reproduce this behavior.

However expected behavior is as follows,

After changing allowed users of a volume through management console, opened volume in MS Windows are still fully accessible unless user logs off from the system.  The session is not closed by Samba.

Admin needs to force restart the volume to destroy opened sessions.
Comment 2 Jacob Shucart 2010-10-29 11:53:35 UTC 
This was a new volume and the first time I connected to it from my Windows 7 64-bit laptop.
Note You need to log in before you can comment on or make changes to this bug.