Closed
Bug 731213
Opened 12 years ago
Closed 11 years ago
Review file uploads & management for Django 1.5 upgrade
Categories
(developer.mozilla.org :: Security, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: groovecoder, Unassigned)
References
Details
(Whiteboard: [subtask] c=Security p=)
One other thing worth noting is that we'll want to carefully review how we manage files, since Django now does not auto-cleanup orphaned files for us.
Assignee | ||
Updated•12 years ago
|
Version: Kuma → unspecified
Assignee | ||
Updated•12 years ago
|
Component: Website → Landing pages
Updated•12 years ago
|
Summary: Review file uploads & management → Review file uploads & management for Django 1.4.1 upgrade
Updated•11 years ago
|
Component: Landing pages → Security
Summary: Review file uploads & management for Django 1.4.1 upgrade → Review file uploads & management for Django 1.5 upgrade
Whiteboard: u=developer c=infrastructure p= → [subtask] c=Security
Updated•11 years ago
|
Whiteboard: [subtask] c=Security → [subtask] c=Security p=
Comment 1•11 years ago
|
||
After going through most of our file-handling code, I don't believe we have anything that'll cause problems. Once in a while we may have files lingering unexpectedly, but if/when we run into that we can probably do a quick and short cron job that finds and cleans them up depending on where they come from.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•