Update Usf doc

README.md

@@ -28,41 +28,47 @@ Do not use this app with volumes containing sensitive data unless you know exact
 - Unlocking volumes using fingerprint authentication
 - Volume auto-locking when the app goes in background
 
-_For upcoming features, see [TODO.md](https://forge.chapril.org/hardcoresushi/DroidFS/src/branch/master/TODO.md)._
+For planned features, see [TODO.md](https://forge.chapril.org/hardcoresushi/DroidFS/src/branch/master/TODO.md).
 
 # Unsafe features
 Some available features are considered risky and are therefore disabled by default. It is strongly recommended that you read the following documentation if you wish to activate one of these options.
 
 <ul>
-  <li><h4>Allow screenshots:</h4>
+  <li><b>Allow screenshots:</b>
+
   Disable the secure flag of DroidFS activities. This will allow you to take screenshots from the app, but will also allow other apps to record the screen while using DroidFS.
 
-  Note: apps with root access don't care about this flag: they can take screenshots or record the screen of any app without any permissions.
+  Note: apps with root access don't care about this flag: they can take screenshots or record the screen of any app without any permissions.</li>
-  </li>
+  <li><b>Allow exporting files:</b>
-  <li><h4>Allow exporting files:</h4>
+
-  Decrypt and write file to disk (external storage). Any app with storage permissions could access exported files.
+  Decrypt and write file to disk (external storage). Any app with storage permissions could access exported files.</li>
-  </li>
+  <li><b>Allow sharing files via the android share menu⁽¹⁾:</b>
-  <li><h4>Allow sharing files via the android share menu*:</h4>
+
-  Decrypt and share file with other apps. These apps could save and send the files thus shared.
+  Decrypt and share file with other apps. These apps could save and send the files thus shared.</li>
-  </li>
+  <li><b>Allow saving password hash using fingerprint:</b>
-  <li><h4>Allow saving password hash using fingerprint:</h4>
+
-  Generate an AES-256 GCM key in the Android Keystore (protected by fingerprint authentication), then use it to encrypt the volume password hash and store it to the DroidFS internal storage. This require Android v6.0+. If your device is not encrypted, extracting the encryption key with physical access may be possible.
+  Generate an AES-256 GCM key in the Android Keystore (protected by fingerprint authentication), then use it to encrypt the volume password hash and store it to the DroidFS internal storage. This require Android v6.0+. If your device is not encrypted, extracting the encryption key with physical access may be possible.</li>
-  </li>
+  <li><b>Disable volume auto-locking:</b> (previously called <i>"Keep volumes open when the app goes in background"</i>)
-  <li><h4>Keep volume open when the app goes in background:</h4>
+
-  Don't close the volume when you leave the app but keep running it in the background. Anyone going back to the activity could have access to the volume.
+  Don't close open volumes when you leave the app. Anyone going back to the application could have access to open volumes. Cryptographic secrets are kept in memory for an undefined amount of time.</li>
-  </li>
+  <li><b>Keep volumes open:</b>
-  <li><h4>Allow opening files with other applications*:</h4>
+  (Different from the old <i>"Keep volumes open when the app goes in background"</i>. Yes it's confusing, sorry)
-  Decrypt and open file using external apps. These apps could save and send the files thus opened.
+
-  </li>
+  Keep the app running as a [foreground service](https://developer.android.com/develop/background-work/services/foreground-services) to maintain volumes open, even when the app is removed from recent tasks.
-  <li><h4>Expose open volumes*:</h4>
+
-  Allow open volumes to be browsed in the system file explorer (<a href="https://developer.android.com/guide/topics/providers/document-provider">DocumentProvider</a> API). Encrypted files can then be selected from other applications, potentially with permanent access. This feature requires <i>"Keep volume open when the app goes in background"</i> to be enabled.
+  This avoid the app from being killed by the system during file operations or while accessing exposed volumes, but this mean cryptographic secrets stay in memory for an undefined amount of time.</li>
-  </li>
+  <li><b>Allow opening files with other applications⁽¹⁾:</b>
-  <li><h4>Grant write access:</h4>
+
-  Files opened with another applications can be modified by them. This applies to both previous unsafe features.
+  Decrypt and open file using external apps. These apps could save and send the files thus opened.</li>
-  </li>
+  <li><b>Expose open volumes⁽¹⁾:</b>
+
+  Allow open volumes to be browsed in the system file explorer (<a href="https://developer.android.com/guide/topics/providers/document-provider">DocumentProvider</a> API). Encrypted files can then be selected from other applications, potentially with permanent access. This feature requires <i>"Disable volume auto-locking"</i>, and works more reliably when <i>"Keep volumes open"</i> is also enabled.</li>
+  <li><b>Grant write access:</b>
+
+  Files opened with another applications can be modified by them. This applies to both previous unsafe features.</li>
 </ul>
 
-\* These features can work in two ways: temporarily writing the plain file to disk (DroidFS internal storage) or sharing it via memory. By default, DroidFS will choose to keep the file only in memory as it's more secure, but will fallback to disk export if the file is too large to be held in memory. This behavior can be changed with the *"Export method"* parameter in the settings. Please note that some applications require the file to be stored on disk, and therefore do not work with memory-exported files.
+⁽¹⁾: These features can work in two ways: temporarily writing the plain file to disk (DroidFS internal storage) or sharing it via memory. By default, DroidFS will choose to keep the file only in memory as it's more secure, but will fallback to disk export if the file is too large to be held in memory. This behavior can be changed with the *"Export method"* parameter in the settings. Please note that some applications require the file to be stored on disk, and therefore do not work with memory-exported files.
 
 # Download
 <a href="https://f-droid.org/packages/sushi.hardcore.droidfs">
@@ -90,20 +96,11 @@ F-Droid APKs should be signed with the F-Droid key. More details [here](https://
 # Permissions
 DroidFS needs some permissions for certain features. However, you are free to deny them if you do not wish to use these features.
 
-<ul>
+- **Read & write access to shared storage**: Required to access volumes located on shared storage.
-  <li><h4>Read & write access to shared storage:</h4>
+- **Biometric/Fingerprint hardware**: Required to encrypt/decrypt password hashes using a fingerprint protected key.
-  Required to access volumes located on shared storage.
+- **Camera**: Required to take encrypted photos or videos directly from the app.
-  </li>
+- **Record audio**: Required if you want sound on video recorded with DroidFS.
-  <li><h4>Biometric/Fingerprint hardware:</h4>
+- **Notifications**: Used to report file operations progress and notify about volumes kept open.
-  Required to encrypt/decrypt password hashes using a fingerprint protected key.
-  </li>
-  <li><h4>Camera:</h4>
-  Required to take encrypted photos or videos directly from the app.
-  </li>
-  <li><h4>Record audio:</h4>
-  Required if you want sound on video recorded with DroidFS.
-  </li>
-</ul>
 
 # Limitations
 DroidFS works as a wrapper around modified versions of the original encrypted container implementations ([libgocryptfs](https://forge.chapril.org/hardcoresushi/libgocryptfs) and [libcryfs](https://forge.chapril.org/hardcoresushi/libcryfs)). These programs were designed to run on standard x86 Linux systems: they access the underlying file system with file paths and syscalls. However, on Android, you can't access files from other applications using file paths. Instead, one has to use the [ContentProvider](https://developer.android.com/guide/topics/providers/content-providers) API. Obviously, neither Gocryptfs nor CryFS support this API. As a result, DroidFS cannot open volumes provided by other applications (such as cloud storage clients). If you want to synchronize your volumes on a cloud, the cloud application must synchronize the encrypted directory from disk.

fastlane/metadata/android/en-US/changelogs/373.txt

@@ -0,0 +1,8 @@
+- Reworked UI for adding volumes
+- New unsafe feature to keep the app running as a foreground service
+- Allow choosing file export method
+- Logcat viewer (for easier debugging)
+- New turkish & chinese-simplified translations
+- UX improvements
+- Bug fixes
+- Translations updates

fastlane/metadata/android/en-US/full_description.txt

@@ -7,6 +7,7 @@ Currently, DroidFS supports the following encrypted containers:
 - Compatible with original encrypted volume implementations
 - Internal support for video, audio, images, text and PDF files
 - Built-in camera to take on-the-fly encrypted photos and videos
+- Ability to expose volumes to other applications
 - Unlocking volumes using fingerprint authentication
 - Volume auto-locking when the app goes in background
 
@@ -15,6 +16,7 @@ Currently, DroidFS supports the following encrypted containers:
 <b>Biometric/Fingerprint hardware:</b> needed to encrypt/decrypt password hashes using a fingerprint protected key.
 <b>Camera:</b> required to take encrypted photos or videos directly from the app.
 <b>Record audio:</b> required if you want sound on videos recorded with DroidFS.
+<b>Notifications:</b> used to report file operations progress and notify about volumes kept open
 
 All of these permissions can be denied if you don't want to use the corresponding feature.