-
Notifications
You must be signed in to change notification settings - Fork 976
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NotImplemented exception thrown on AES unzip. #188
Comments
Here is an example zip. the password is "aaa'. |
I have this same problem with the following code: var zipFile = new ZipFile(zipStream)
{
Password = "Some Encryption Password"
};
foreach (ZipEntry entry in zipFile)
{
if (!entry.IsFile) continue;
string content;
var zipInputStream = zipFile.GetInputStream(entry);
// Read file contents
using (var s = new StreamReader(zipInputStream, Encoding.UTF8))
{
content = s.ReadToEnd(); // The file content is properly read without problems
} // exception is thrown here
} It seems to me the exception occurs here:
|
So what should someone do, given this bug? I can get the input stream and read from it. But we can't close it. Should we call it and catch the exception, or just leave it open? If we're unzipping a large file, I'm concerned about leaving all those stream open. Or, is it sufficient to close the contraining stream (e.g. MemoryStream) that is passed to ZipFile ? |
I don't know. This is planned to be fixed for v1.1, and is currently listed as not working as per #35. I have not been able to work on it for a while though. |
I cannot reproduce this problem in 1.2.0. I don't know in which version it was fixed. |
It was fixed in v1.1, thanks for updating (closing) the issue! |
Steps to reproduce
Expected behavior
The bytes are read from the stream successfully, so the functionality IS implemented. The exception should not be thrown.
Actual behavior
NotImplemented exception is thrown.
Version of SharpZipLib
0.86.0 nuget package.
Obtained from (place an x between the brackets for all that apply)
The text was updated successfully, but these errors were encountered: