Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Directory permission Icons misleading when connected to non-UNIX servers #957

Closed
cyberduck opened this issue Nov 17, 2006 · 2 comments
Closed
Assignees
Labels
Milestone

Comments

@cyberduck
Copy link
Collaborator

64c7943 created the issue

Hi,

This is regarding the following enhancement that was added in 2.6
[Feature] Marking write-only and non-accessible directories with special icon as in Finder.app

I work for a university and we run an FTP Server using Gene6 FTP Server 3.8 on Windows Server 2003, we are using Active Directory/NTFS permissions to manage users and user permissions, so Unix CHMOD permissions do not apply at all.

Starting with Cyberduck 2.6 which added the marking of write-only and non-accessible folders.

It displays a red icon(which I presume to be the one for non-writable folders) on every folder, even if the user actually has full read and write permissions. This bug doesn't actually prevent the user from writing to the folder. It does however confuse our students, so we were forced to go back to 2.5.5.

Would it be possible to have an option to completely turn off the marking completely and revert it back to the way 2.5.5 did things, atleast until the permission detection works properly.

Thanks,

@cyberduck
Copy link
Collaborator Author

@dkocher commented

As of 7ac1f62 you can use set the property browser.markInaccessibleFolders to disalbe the marking of write-only and inaccessible folders. Use

defaults write ch.sudo.cyberduck browser.markInaccessibleFolders false

@cyberduck
Copy link
Collaborator Author

@dkocher commented

See changes in c002037.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants