-
Notifications
You must be signed in to change notification settings - Fork 243
FOUR-26751: Make the dangerous_extensions verification configurable #8537
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
Conversation
|
|
QA server K8S was successfully deployed https://ci-96fe8ade36.engk8s.processmaker.net |
|
QA server K8S was successfully deployed https://ci-96fe8ade36.engk8s.processmaker.net |
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.
|
@ana-mauricio |
|
The control UPLOAD A FILE in public files has some restriccions about the extensions. This is not related with changes. |
ana-mauricio
left a comment
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.
The following ticket doc was created DOC-3723: Add documentation to Public Files to allowed_extensions and dangerous_extensions
With this clarification, this configuration of dangerous and allowed extensions does not apply to public files.
So the ticket is approved.







Issue & Reproduction Steps
Make the dangerous_extensions verification configurable
Solution
Per default all is true.
In order to disable the validation add those in the .env
How to Test
Related Tickets & Packages
Code Review Checklist
ci:deploy
ci:ENABLE_DANGEROUS_VALIDATION=false
ci:ENABLE_MIME_VALIDATION=false
ci:ENABLE_EXTENSION_VALIDATION=false