Cyberduck
Mountain Duck
CLIOpened on May 6, 2015 at 5:49:24 PM
Closed on May 7, 2015 at 8:13:31 AM
#8807 closed enhancement (wontfix)
Add "Read Only" option to a connection
| Reported by: | ethanms | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | |
| Component: | core | Version: | 4.7 |
| Severity: | trivial | Keywords: | |
| Cc: | Architecture: | Intel | |
| Platform: | Mac OS X 10.10 |
Description
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
Change History (1)
comment:1 Changed on May 7, 2015 at 8:13:31 AM by dkocher
- Resolution set to wontfix
- Status changed from new to closed
Download in other formats:
Powered by Trac 1.0.4
By Edgewall Software.
Visit the Trac open source project at
http://trac.edgewall.org/
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.