While our Security Statement mentions that the users are responsible for the protection of the authentication means and all actions performed under their profile, some clients would prefer even stronger security included into Memsource. They would like to be able to use encrypted MXLIFF files that could be opened only using the credentials.
Current behavior:
It's not possible to encrypt MXLIFF files.
Workaround:
Use any archival tool (like WinRAR) to password protect the MXLIFF files once you are done working.
Requested behavior:
It's possible to download encrypted MXLIFF files.
1 comment
Here's my view:
It does not have to be encrypted at the time when MXLIFF files are downloaded, but it needs to be encrypted after being downloaded for the security reason.
Otherwise, the translation company is going to prohibit us translators from using Desktop Editor, which is not aligned with your company strategy, i.e., both Web and Desktop Editors should be available to anyone, especially given the fact that Desktop Editor has its own unique advantages and any translation company is not entitled to prohibit us from using it.
Just like the encryption of WORD and EXCEL files, a simple way of password protecting MXLIFF files will be good enough; no need to develop a complicated feature.
Please sign in to leave a comment.