Closed (won't fix)
Project:
Web File Manager
Version:
6.x-2.12
Component:
User interface
Priority:
Critical
Category:
Support request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
20 Apr 2010 at 13:00 UTC
Updated:
22 Apr 2010 at 13:30 UTC
Comments
Comment #1
cgmonroe commentedChanged to support request because IMHO this is outside the scope of what WebFM is designed for.
If you think about what you have done, it's understandable why this happens. You have a link which looks like a subdirectory in the webfm root that goes to its parent... then when you "walk" the tree, you look at the subdirectory link, see the webfm root directory, then see the link subdirectory again, then see the parent directory and... continue ad nausium.
IMHO, it's a big security risk to allow WebFM to "play" outside it's sandbox. It shouldn't allow this to happen by default. E.g., someone breaks into your admin account, sets the WebFM root directory to your system root, and installs all sorts of nasty things using WebFM.. not nice.
That said, if you don't care about security.. somewhere in the issues is a thread about allowing ".." to be used in the webfm root directory property. I think it was a change to the regex test. This would allow you to specify ".." as your WebFM root and access the files directory without recursion.
Comment #2
robmilne commentedJust checking in after a holiday break. WebFM isn't designed to operate on ".." paths - end of story. I will not allow this module to monkey with the files of other modules - unless of course other modules choose to place their files inside the WebFM space.
Comment #3
robmilne commented