View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001063||mantisbt||installation||public||2001-10-29 06:30||2014-10-02 18:21|
|Status||closed||Resolution||no change required|
|Summary||0001063: About file uploads|
I think the following folder should be created at installation:
When a new project is created, say "New Website", the following folders are created automatically.
The project upload path should default to $MANTIS/uploads/projects/new_website, but making the /uploads/projects part not editable from the textbox.
I think that would lessen the possibility of shooting oneself in the foot.
Also would be nice if when deleting the project there was a checkbox saying "Delete uploaded files folder?"
|Tags||No tags attached.|
Sounds good. I'll be improving this for the 0.16.0 release when I also get db upload/download working.
Uploading to the same directory where all .php files are stored is a serious security hazard: Anybody could upload a .php file and then execute it...
What is the status of this ?
upload to database does work well.
Since the project name can be changed, I think it's necesary to use the id number instead.
where 34 is the project id, which remains constant
Some of these concerns have been answered, the rest we should probably still look into (i.e. removing uploaded files, if that isn't already implemented).
Looks like the feature I reported (0004627) is related to this one... However, in aarjona's description... he talks about $MANTIS/uploads/projects (I'll call this $UPLOADS_BASE_DIR). I really think that location should be configurable in the config file... so that all projects save files to the same place, and the path in $UPLOADS_BASE_DIR isn't written to the database. That way you can move where your files are saved by changing $UPLOADS_BASE_DIR and the database doesnt have the full path to where the file "used" to be.
Probably not the right place to put this quesion, but:
Is there a good reason, why the the filenames that are generated are
I would prefer to see the original file name.
I saw in CVS that this is considered a security issue, as one could upload a file and executed it. Obviously it is safer if the files are not uploaded to a directory that could be accessed via www, but this has to be assured by the configuration so it is probably better, to fix is issue even for bad configurations.
My suggestion would be:
Append the filename with an md5 sum. So one can see the original filename and still there is no security problem.
replace in file_api.php
(The above lines are wrapped by a mantis preformatted text bug 0004762)
I'm resolving this issue as "no change required" - I believe the functionality described in this issue is actually implemented in the latest versions of Mantis - albeit, you need to use the per-project configuration to set custom paths for each project.
In addition this was added before the ability to save files in the database existed, so may be less relevant in a modern mantis installation.
|2004-08-09 05:10||jlatour||Note Added: 0006853|
|2004-08-09 05:11||jlatour||Relationship added||child of 0004181|
|2004-10-15 09:39||kgrubbs||Note Added: 0008057|
|2004-11-09 05:45||polzin||Note Added: 0008299|
|2004-11-09 05:46||polzin||Note Edited: 0008299|
|2004-11-09 05:53||polzin||Note Edited: 0008299|
|2004-11-09 05:58||polzin||Note Added: 0008300|
|2009-05-31 12:19||grangeway||Assigned To||prescience =>|
|2009-05-31 12:19||grangeway||Status||assigned => acknowledged|
|2011-12-31 11:22||dregad||Relationship added||related to 0007186|
|2012-08-08 09:59||dregad||Relationship added||related to 0012942|
|2014-09-22 15:33||grangeway||Note Added: 0041273|
|2014-09-22 15:33||grangeway||Status||acknowledged => resolved|
|2014-09-22 15:33||grangeway||Resolution||open => no change required|
|2014-09-22 15:33||grangeway||Assigned To||=> grangeway|
|2014-10-02 18:21||atrol||Status||resolved => closed|