| Summary: | Cannot access symlink | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Paul Lesiecki <ntgdpl> |
| Component: | Server | Assignee: | Project Inbox <orion.server-inbox> |
| Status: | RESOLVED WORKSFORME | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | ahunter.eclipse |
| Version: | 4.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Paul Lesiecki
(In reply to Missing name from comment #0) > 5. notice notification "Forbidden: /user-OrionContent/path1/linkToPath2/" This works as currently designed. We prevent the creation and execution against files and folders on the server that are symbolic links. Any explanation why is that? It is disabled because of security risk. I could imagine allowing this for the admin specified paths but really the server storage location should be opaque for the end user - end user will not ever know absolute servers and so can't meaningfully use symlinks. Maybe you can describe the kind of scenario where you want this - is it a single user server running on localhost? In my use case, I as admin, I want to allow end users (on prepared accounts) to edit only specific files (in only selected directories). Instead of adding each path to allowed paths I tried set only one allowed path and then inside that path I made symlinks to directories which I want give access to. |