-
Notifications
You must be signed in to change notification settings - Fork 99
Simple Whitelist for File Extensions #122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution! I've added a little feedback inline..
| // Filter extensions if whitelist available | ||
| var whitelist = self.server.options.allowedExtensions; | ||
| var accepted = true; | ||
| if (whitelist && typeof whitelist === 'object' && Array.isArray(whitelist) && whitelist.length) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Array.isArray(whitelist) && whitelist.length should be sufficient, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, if it's an object and has a length, why check for array-ity?
| if (whitelist && typeof whitelist === 'object' && Array.isArray(whitelist) && whitelist.length) { | ||
| accepted = false; | ||
| whitelist.forEach(function (ext) { | ||
| if (fileto.endsWith(ext)) accepted = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you check what version of Node added support for endsWith since we want to make sure we don't break existing installations..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should allow RegExps too, or Cartesian product will explode for relatively simple stuff like /\.(html?|jpe?g|png|gif|p[pgx]m|txt)(\.((t?g|7)z|zip|tar(\.[g7]z|))|)$/. And that doesn't even yet include rules to allow some parts to be all-uppercase when using tar. ;-)
| whitelist.forEach(function (ext) { | ||
| if (filename.endsWith(ext)) accepted = true; | ||
| }); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we're repeating this whitelist checking logic, I think it would make sense to put it in a function so we can do: var accepted = checkWhitelist(self.server.options.allowedExtensions, filename);
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also it should be have "extension" in its name because we might add other whitelists in the future.
In many cases, you want to limit the file extensions saved on the server to prevent executables or other formats from being uploaded.