The CHAT_INVALID_FILE_EXTS parameter can currently be used to control which file types may not be used in the chat. If you attach importance to security, you will hardly be able to keep up with the addition of potentially dangerous file extensions.
For IT security reasons, it is better to use an allowlist instead of this blocklist. It would be great if the “CHAT_INVALID_FILE_EXTS” parameter could be replaced by a “CHAT_VALID_FILE_EXTS” parameter.
This would make it very easy to restrict file exchange to the widely used graphic and exchange formats:
.jpg, .jpeg, .gif, .png, .tif, .tiff, .bmp, .pdf
The vast majority of users would not even notice that the file formats are restricted, but there would be a relevant gain for IT security and data protection.
For IT security reasons, it is better to use an allowlist instead of this blocklist. It would be great if the “CHAT_INVALID_FILE_EXTS” parameter could be replaced by a “CHAT_VALID_FILE_EXTS” parameter.
This would make it very easy to restrict file exchange to the widely used graphic and exchange formats:
.jpg, .jpeg, .gif, .png, .tif, .tiff, .bmp, .pdf
The vast majority of users would not even notice that the file formats are restricted, but there would be a relevant gain for IT security and data protection.
Upvote
1
