Protecting access to the application with a password
Sophos Mobile Encryption now allows to define an application password that has
to be entered to access Sophos Mobile Encryption. An additional recovery
password can be generated to reset the application password in the case the
password is forgotten.
Upload of encrypted files to the cloud storage providers
Sophos Mobile Encryption is now able to receive and encrypt files from other
third-party applications (via open with). The encrypted files are uploaded to a
linked cloud storage provider or alternatively stored in an app-internal local
storage. The user can select an already used key (when the keychain feature is
enabled) or can define a new passphrase from which the encryption key is
derived. Furthermore, the user can move files from the local storage to a
linked cloud storage provider.
Sophos Mobile Encryption runs on the following platforms:
Compatible devices have to run Apple iOS 5.x or iOS 6.x or iOS 7.x.
Sophos Mobile Encryption supports following storage providers:
Installation
Installation of the application must be done via the Apple Itunes App Store.
Dropbox
Authentication
Once successfully linked to a Dropbox account, no more password input is required
to get access to the files in the linked Dropbox. Even if the password for this
Dropbox account is changed on another system or via the Dropbox web site,
presenting this new password is not required on any of the linked system nor do
these systems have to be linked again. In case access to the Dropbox has to be
withdrawn reliably (e.g. because a mobile device is lost), the device should be
un-linked from the given Dropbox account via the Dropbox web site and thus be
no longer allowed to access the data.
File
Sync
Files stored on the mobile device are updated automatically whenever modified
in the cloud. Some file attributes like the file size and modification date are
used to detect any changes. In case a previously encrypted file is encrypted
using a different key, the file will not be
synchronized to the client. Reason is, that the content of the file remains
unchanged, as well as the file's attributes and therefore a sync is not
triggered.
Accepting
EULA Crash
After installing SME and accepting the EULA, SME might crash once if and only
if all available Cloud Service Providers are linked. Restarting the application
resolves the problem and prevents future crashes. Reason for this issue is a
bug in the iOS code for WebView which can't be fixed by SME.
Possible app crash when uploading a favorite file from local storage to Google Drive where the file already exists
If the user uploads a favorite file to Google Drive that already exists on Google Drive, a crash can occur when the user leaves the upload view via the back button and then interacts with the occuring confirmation dialog. After restarting the app, the upload has to be done again.
Canceling the download of a file may not allow to download it again when the user browses into another folder and comes back to download the one file again
If the user cancels the download of a file and browses to another folder and comes back to the same folder, it might happen that the user cannot start the download of the file again that he canceled before. After starting the download of another file, the one file can be downloaded again.
When file download from cloud storage is stopped because the user navigated to another folder, the same file download cannot be started immediatly after returning back to its folder
Technical support
You can find technical support for Sophos products in any of these ways:
Copyright © 2014 Sophos Ltd. All rights reserved.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise unless you are either a valid licensee where the documentation can be reproduced in accordance with the license terms or you otherwise have the prior permission in writing of the copyright owner.
Sophos is a registered trademark of Sophos Ltd. All other product and company names mentioned are trademarks or registered trademarks of their respective owners.