You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, I'm porting a pretty old application which utilizes 7zip and AES. Thing is, for AES to work the buffer needs to be of length dividable by 16. This is a problem, because adding trailing zeroes (like the old java implementation did) crashes the program with Found end-of-stream marker but more bytes are available error. Handling the error doesn't help, because output stream is empty. Would it be a problem to add support for such behaviour? My project really depends on it :)
The text was updated successfully, but these errors were encountered:
#90 this fixes it for me, but I'm not sure whether you'd accept such solution as it's more of a quick dirty hack than a solution. Maybe a feature flag like allow-trailing-bytes would be better solution here
Hey, I'm porting a pretty old application which utilizes 7zip and AES. Thing is, for AES to work the buffer needs to be of length dividable by 16. This is a problem, because adding trailing zeroes (like the old java implementation did) crashes the program with
Found end-of-stream marker but more bytes are available
error. Handling the error doesn't help, because output stream is empty. Would it be a problem to add support for such behaviour? My project really depends on it :)The text was updated successfully, but these errors were encountered: