I'm trying to add a .test file for the CustomError module and I'm being warned that I can't attach files with a .test extension. Please could that be added as an allowed extension?
I'm trying to add a .test file for the CustomError module and I'm being warned that I can't attach files with a .test extension. Please could that be added as an allowed extension?
Comments
Comment #1
geodaniel commentedComment #2
michelleHijacking your issue because this has been bugging me lately. :)
In addition to the .test for the OP, could we have .inc added? Getting tired of having to add a .txt to the end of it.
Thanks,
Michelle
Comment #3
avpadernoAllowing to attach a file with extension inc seems a reasonable request, to me.
As both the extensions are used for development files, I think it would be good to have them added. Also, files with those extensions are harmless, for a computer; I mean that an OS doesn't try to execute them, normally.
+1 from me.
Comment #4
avpadernoDoes anybody else have a thought about this?
As Drupal.org is a site for developers, it should at least allow to use those extensions that are normally used for PHP code (especially from Drupal).
Comment #5
gerhard killesreiter commentedI guess somebody needs to add these.
Comment #6
avpadernoI am willing to help in such tasks; there are other feature requests that needs a user to change the settings (such as the ones about the tags allowed in a input format), and I can accomplish such tasks.
Comment #7
dwwWhat needs to happen here is someone needs to audit and test how various httpds and browsers handle these file extensions. The scary thing about allowing new file extensions in uploads is that in some combinations, the new extensions can be automatically loaded and evaluated, leading to XSS or code execution vulnerabilities. So, if you want direct .test and .inc uploads, you have to show that they're safe. Thanks!
Comment #8
avpadernoI made some simple tests on Mac OS X, and Windows.
It's not clear to me if we would be worried if something would happen in the client side, or the server side.
If something weird would happen at server side, then it would be a bug in Drupal code, and I am sure it should have been already discovered (as I am sure that the proposed extensions don't activate a dormant bug in Drupal code); if we would be worried about something weird happening on client side, then the default extensions would not allow to attach a or a file, considering that those files can contain malicious code in the included macros.
Looking at the allowed extensions, I notice that the extension is already allowed. Does that extension create less problems than the extension ?
Comment #9
dddave commentedClosing old, stale issues as part of the webmaster's clean-up spring of DrupalCon Prague.