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

Jump to bottom

Add "Read Only" option to a connection #8807

Closed
cyberduck opened this issue May 6, 2015 · 1 comment
Closed

Add "Read Only" option to a connection #8807

cyberduck opened this issue May 6, 2015 · 1 comment
Labels
core enhancement low priority wontfix

Comments

@cyberduck
Copy link
Collaborator

1491519 created the issue

I sometimes have reason to retrieve files from our production server but want to be sure I do not make changes at the time.

It's impractical for me to create a user with read-only privilege, but it would be nice to have a client that would restrict operation to only read-type operations.

For example, a "Read Only" mode that can be associated with connecting a certain server where commands that would cause changes on the remote side are either not accepted, or are at least are met with a "Are you sure? You're in read-only mode." type of confirmation prompt.

Thank you
@cyberduck
Copy link
Collaborator Author

@dkocher commented

We have prompts when overwriting files per default for both rename and upload. Really restricting access is not technically feasible for a client and you can never be sure the client will not eventually write anyway therefore it is much safer to have a user with restricted permissions on the server.

@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.
Assignees
No one assigned
Labels
core enhancement low priority wontfix
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cyberduck