#28540: When you save three or more ImageField in admin file perm = 0o600
-------------------------------------+-------------------------------------
Reporter: Yaroslav Demidenko | Owner: nobody
Type: Bug | Status: new
Component: File | Version: 1.11
uploads/storage |
Severity: Normal | Resolution:
Keywords: ImageField, save, | Triage Stage:
permissions | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simen Heggestøyl):
* cc: Simen Heggestøyl (added)
* status: closed => new
* resolution: needsinfo =>
Comment:
We've hit the same issue, and I've identified
f734e2d4b2fc4391a4d097b80357724815c1d414 as the offending commit.
The issue seems to be that when `FILE_UPLOAD_PERMISSIONS` is `None`, the
default system permissions are used. This worked fine for us, because our
system default is 644, which is what we wanted. After
f734e2d4b2fc4391a4d097b80357724815c1d414 however, when the uploaded file
is sufficiently large, the system's permissions for temporary files is
used instead (which was 600 in our case).
Setting `FILE_UPLOAD_PERMISSIONS` explicitly fixes the issue, but I think
this behavioral change should be mentioned in the release notes.
--
Ticket URL: <https://code.djangoproject.com/ticket/28540#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.e22bfce2a0a2ab079cc19d26a79dff36%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
