Fixed a bug related to uploading end to end encrypted file.
E2EE files and uploads are uploaded as files of mime type `application/octet-stream` as we can't reveal the mime type of actual content since it is encrypted and has to be kept confidential.
The server resolves the mime type of encrypted file as `application/octet-stream` but it wasn't playing nicely with existing settings related to whitelisted and blacklisted media types.
E2EE files upload was getting blocked if `application/octet-stream` is not a whitelisted media type.
Now this PR solves this issue by always accepting E2EE uploads even if `application/octet-stream` is not whitelisted but it will block the upload if `application/octet-stream` is black listed.
"E2E_Enabled_Default_DirectRooms":"Enable encryption for Direct Rooms by default",
"E2E_Enabled_Default_PrivateRooms":"Enable encryption for Private Rooms by default",
"E2E_Enable_Encrypt_Files":"Encrypt files",
"E2E_Enable_Encrypt_Files_Description":"Encrypt files sent inside encrypted rooms. Check for possible conflicts in [file upload settings.](admin/settings/FileUpload)",
"E2E_Encryption_Password_Explanation":"You can now create encrypted private groups and direct messages. You may also change existing private groups or DMs to encrypted.<br/><br/>This is end-to-end encryption so the key to encode/decode your messages will not be saved on the server. For that reason you need to store your password somewhere safe. You will be required to enter it on other devices you wish to use e2e encryption on.",
"Encrypted_field_hint":"Messages are end-to-end encrypted, search will not work and notifications may not show message content",
"Encrypted_file_not_allowed":"Encrypted file not allowed",
"Email_sent":"Email sent",
"Email_verification_isnt_required":"Email verification to login is not required. To require, enable setting in <a href=\"{{url}}\">Accounts</a> > Registration",