Section 4.2 of the specification outlines how the edit list is applied. In the example, it says that the last keep value "[...] could actually be left out as it extends all the way to the end of the file." While testing my PR #88, I noticed that the last keep value is not optional in this implementation. Is this a potential interoperability issue?
To Reproduce
Encrypt value "1234" with edit list [3].
Expected behavior
Expecting first 3 bytes to be discarded. Decrypted result should therefore be "4".
Actual behavior
All data is discarded resulting to an empty result. Changing the edit list to [3,1] produces the expected result "4".
Describe the bug
Section 4.2 of the specification outlines how the edit list is applied. In the example, it says that the last keep value "[...] could actually be left out as it extends all the way to the end of the file." While testing my PR #88, I noticed that the last keep value is not optional in this implementation. Is this a potential interoperability issue?
To Reproduce
Encrypt value "1234" with edit list [3].
Expected behavior
Expecting first 3 bytes to be discarded. Decrypted result should therefore be "4".
Actual behavior
All data is discarded resulting to an empty result. Changing the edit list to [3,1] produces the expected result "4".
Sample code