Update from 1.5.3 to the latest version is broken

[stevenbeckett]

I’ve recently updated from 1.5.3. to the latest version and seeing a breaking issues with EtM_DecryptTransform and EtM_DecryptTransform .

Looking at the history I can see there is a breaking change in the API signature of both functions (the default chunkNumber has been removed). No big deal for us as we do not use this. However, this still causes an exception to be thrown so the implementation has obviously also changed.

The question is, how do we supply an upgrade path for the users of our App who can have thousands of files encrypted with version 1.5.3?

[philipag]

This was already discussed in #33
Note that I added a PR #45 to again provide seeking capability.

[sdrapkin]

This was already discussed in #33, as @philipag mentioned. IMHO the likely options for you are:

1. Do nothing (keep using v1.5.3)
2. Opportunistically or holistically decrypt with v1.5.3 and re-encrypt with latest.
3. Support both, and use v1.5.3 to decrypt older data only, while using latest for all new encrypted data.