The app (both mobile and desktop) successfully creates a sharable link (with an external S3 provider), but throws an exception the moment I want to download it, when you click download, it prompts the file system window when you wanna download smth (on desktop, on mobile directly does nothing), but won't do it(edited)
Hi @sontec,
Thanks for your report.
It seems that you have E2E enabled (V2 cipher) and updated shared files after creating share.
Every file version has its unique encryption key.
Once you upload new version (e.g. modification to existing file), new encryption key is used.
This doesn't match the encryption key that was "extracted" for the share itself, hence data can't be decrypted until share is created again.
There are some workarounds that we plan to implement.
E.g. we could track "shared" resources from the S3Drive and regenerate the share data to include JSON keys.
We don't plan implementing it until we solve the 7-day expiration limit, which requires creative approach using link shortener.
In the meantime you can consider using our managed S3 which doesn't have above limitations since it's tightly integrated with S3Drive.
I've created feature request to track this feature request: https://s3drive.canny.io/feature-requests/p/updating-files-for-encrypted-v2-share-results-in-invalid-key-iv-error
Once user creates a share and then modifies the file contents, it makes the new file version not downloadable/previewable.
8:17 AM
Additionally we plan to implement possibility of using external S3 and routing it through our back-ends which would "give it" most of the possibilities that our managed S3 have.
This wouldn't break any E2E guarantees since it would still happen client-side.
1