Difference between revisions of "V3 Appliance Insufficient Permissions"
m (1 revision imported) |
|||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{template:default}} | {{template:default}} | ||
| − | [[Category: | + | [[Category:Version 3 Appliance]] |
=WinSCP and Insufficient Permissions= | =WinSCP and Insufficient Permissions= | ||
Latest revision as of 09:38, 18 May 2017
WinSCP and Insufficient Permissions
In versions prior to V3, arbitrary files could be accessed (or replaced) using WinSCP. In V3, this has changed, and the admin user needs the relevant permissions to access or replace files. Most files should still be accessible from WinSCP as usual, but some may require special methods.
Commandline access
Any file can be recovered using WinSCP using commandline access and a storage space, /support/store. This space is owned by the admin user, and can be used for storing files to WinSCP out.
Suppose we wish to access a file within the folder inaccessible, which the admin user does not have access to. We cannot gain privileges from within WinSCP, so we log on to the CMI using a separate instance, and access the command line using Tools -> Commandline. We can then access “inaccessible”.
We can then copy very_important_file into /support/store (so that the admin user can see it) and give the admin user read permissions (so that we can WinSCP it out).
