sovworks / edsexfat Goto Github PK

Having installed the ExFat module to EDS Lite on a mobile device running Android 11, then tested interchanging Veracrypt-format containers with Mac computers (both M1 and Intel versions) running Mac OS Big Sur (v11.1), the following was observed:

1. A container created on a Mac with Veracrypt (v1.24-update8) with ExFat format could be opened with EDS Lite under Android, but a message stating "the list is empty" was displayed - ie, no files were visible.
2. A container created within EDS Lite in Vercacrypt format could be written to on the Android device, and this container could be opened by Veracrypt on the Mac computers, apparently normally (including indicating that the volume was writable), but from within Mac OS the volume was shown to be read-only - although the files written on the Android device were visible. The 'first aid' function of Disk Utility on the Macs indicated that the file system was unrepairable.
3. The container created by EDS, and decrypted by Veracrypt, was (as a decrypted volume) then erased and re-formatted to ExFat on the Mac. Files loaded to this volume, following encryption by Veracrypt and subsequent decryption by EDS, were no longer visible under EDS.

There appears to be an incompatibility between the Sovworks ExFat module implementation and the Mac ExFat (at least Big Sur) implementation. This was not tested with other Mac OS versions.