Bug 8688 - Renaming a directory on samba >= 3.5.2 changes group-permissions of these
Renaming a directory on samba >= 3.5.2 changes group-permissions of these
Status: RESOLVED INVALID
Product: Samba 3.6
Classification: Unclassified
Component: File services
3.6.1
x64 Linux
: P2 critical
: ---
Assigned To: Volker Lendecke
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-01-04 15:23 UTC by heinz hoelzl
Modified: 2012-05-03 11:08 UTC (History)
1 user (show)

See Also:


Attachments
smb.conf + log.smbd (119.14 KB, application/octet-stream)
2012-01-04 15:23 UTC, heinz hoelzl
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description heinz hoelzl 2012-01-04 15:23:20 UTC
Created attachment 7225 [details]
smb.conf + log.smbd

Renaming a directory on samba >= 3.5.2 changes group-permissions of these. Renaming files works fine.
(tested with samba 3.5.2, 3.5.3, 3.5.4 and 3.6.1.  -  samba version <= 3.5.1 works fine)

To reproduce do the following:
- create a directory named "newdir" and change it's permissions to 750
- then rename it to "renameddir"
- now the permissions are 770

in detail:

pagh:/ # smbclient -V
Version 3.6.1

pagh:/ # ls -dl /samba/sys/user/apl/newdir
drwxr-x--- 2 heinz_sgv users 4096 2012-01-04 11:20 /samba/sys/user/apl/newdir

pagh:/ # smbclient //pagh.klingons.gvcc.net/sys -k -D /user/apl -c "rename newdir renameddir"
Domain=[GVCC.NET] OS=[Unix] Server=[Samba 3.6.1]

pagh:/ # ls -dl /samba/sys/user/apl/renameddir
drwxrwx--- 2 heinz_sgv users 4096 2012-01-04 11:20 /samba/sys/user/apl/renameddir


pagh:/ # smbclient -V
Version 3.5.0

pagh:/ # ls -dl /samba/sys/user/apl/newdir
drwxr-x--- 2 heinz_sgv users 4096 2012-01-04 11:20 /samba/sys/user/apl/newdir

pagh:/ # smbclient //pagh.klingons.gvcc.net/sys -k -D /user/apl -c "rename newdir renameddir"
Domain=[GVCC.NET] OS=[Unix] Server=[Samba 3.5.0]

pagh:/ # ls -dl /samba/sys/user/apl/renameddir
drwxr-x--- 2 heinz_sgv users 4096 2012-01-04 11:20 /samba/sys/user/apl/renameddir



same issue with smbclient and windows-client
Comment 1 heinz hoelzl 2012-05-02 13:03:16 UTC
i have this problem only if the owner of the directory renames the directory.
if someone else renames the directory, everything works fine