Since last Seafile iOS app update to version 2.9.31 a few days ago I’m missing the local decryption option. It’s required for photo upload to an encrypted library. Reinstallation of the app did not bring the option back. Does anybody else missed this option and has an idea how to bring it back?
1 Like
I found the git commit that removes the local decryption. See push at github haiwen/seafile-iOS/pull/398 (sorry I’m not allowed to post links).
Now the question is: Why was it removed?
Encrypted libraries can not be used as photo upload target with the current client. If you try it the error message still indicates that local decryption needs to be activated. But this option does not exist any more.
In addition upload without enabling “Upload HEIC” results in HEIC files with file ending .JPG. Looks like a poorly tested commit.
I am experiencing the same issue, and I was searching for this option, but it’s not there anymore.
Hello guys,
yes, i miss the “local decryption” button as well but i also experienced issues with file-upload for picures greather than 2 mb.
Upload seems to be fine but afterwards thumbnail cannot be generated AND file is not readable if i want to download the picture afterwards on windows or other machines.
iOS app version 2.9.32 fixes the broken upload for JPG files on my device. Local decryption is still not available.
As a workaround, I used an unencrypted library which is fine for a Seafile installation that’s just used locally. But I still don’t understand why there is a regression. Maybe local decryption is not secure?
We are working to improve our security measures. As part of these efforts, the local decryption feature is temporarily unavailable. For this reason, backing up photos to encrypted directories is not currently supported. Due to the current limitations, we recommend backing up your photos to a non-encrypted directory as an alternative solution. We apologize for any inconvenience this may cause.
Thank you for clarifying that local decryption has been disabled.
I understand that you’re aiming to enhance security, but removing a feature without prior notice is poor practice. I couldn’t find a changelog or README for the Seafile iOS app that explains or even mentions this change. This lack of transparency undermines my confidence in Seafile as a stable and secure solution.
Disabling the local decryption feature without a clear explanation makes it seem as though you’ve identified a security weakness and are addressing it by removing the feature altogether. While I understand the concern that poor security is worse than no security, users may feel safe when they are not.
Up until now, I’ve found Seafile to be a stable and secure file transfer solution that meets my needs. The encrypted libraries feature, in particular, makes Seafile quite unique. However, removing this feature without explanation makes me reconsider. If one user is raising this concern, it’s likely that many others share the same thoughts but don’t report it on the forum or GitHub.
Thank you for taking the time to share your thoughts with us. Your feedback is invaluable to us as we strive to improve the Seafile experience.
We understand that removing the local decryption feature without providing clear notice was a misstep on our part. We sincerely apologize for any inconvenience this may have caused. We’re working hard to enhance our communication channels so that you’re always in the loop about changes to Seafile.
Thanks again for your input. Your feedback is helping us shape the future of Seafile.