You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Describe the bug
In the latest Windows version of Cyberduck – version 8.5.2 (38799) – when I select a remote server directory and try to recursively change file permissions for that directory, only the top directory's permissions are changed. None of the child files or subdirectories are modified.
By comparison, trying exactly the same operation in the latest Mac version – also Version 8.5.2 (38799) – works properly. I tried this Mac test on the same remote server directory.
Steps to reproduce the behavior:
Install a fresh copy of Cyberduck for Windows and keep all default settings.
Connect to a server over SFTP with username and password (or username and ssh key).
Create a directory on the server (let's call it "permission-test-dir") with some nested files and subdirectories, making sure that you're creating this directory in a place where you have the necessary permissions to create new files.
Right click on "permission-test-dir" and select "Info".
In the dialog that opens, select the "Permissions" tab.
Type in the new, desired permission value (I've done tests with 770, 771, 776, and other variations).
Click "Apply changes recursively".
Click "Continue" on the prompt that follows. (I am only presented with this prompt once.)
Right click on "permission-test-dir" and select "Refresh" (to ensure that we're looking at the latest permission state).
Observe that "permission-test-dir" permissions have changed to the new value (good).
Observe that permissions for files and subdirectories inside "permission-test-dir" have NOT been recursively changed to the desired value (bad).
I also wanted to note here that in step 8, when trying the same test in the Mac version, I am prompted with more than one "Continue" prompt – one for the directory I am trying to modify, and an additional one for each of the subdirectories.
In the "Steps to reproduce" above, I would have expected that in step 11, all child files and subdirectories inside "permission-test-dir" would have been updated to have the same permissions as "permission-test-dir".
Desktop (please complete the following information):
OS: Verified failure case on Windows 11 and Windows 10.
Cyberduck Version 8.5.2 (38799)
No problem in Cyberduck 8.5.2 (38799) on macOS 12.6.2.
My Cyberduck log file was empty.
The text was updated successfully, but these errors were encountered: