-
Notifications
You must be signed in to change notification settings - Fork 125
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
Digest exception when using a protected zip file (with password) in the application package #276
Comments
Hi @serge-xav, in my opinion computing zip file digest in a robust way is an important improvement. So #275 is the implication of a change to an unsafe implementation. For your mentioned bug here, the best solution would be a fallback to the default digest calculcation, when the zip file is encrypted. Another solution would be to change the extension to ".zip.dat", so getdown don't tries to open the file. |
Hi @bekoenig, thanks for your comment. |
In the next weeks getdown 2.0.0 will be released with different group-id (see bekoenig/getdown#1). This version is feature complete and waits for final release. After this, I can implement this fallback in
|
Hi again Benjamin, I did not see this announcment before, that's good news to see Getdown up and living. Do you want me to also create the issue on your project ? |
You are welcome to open a new issue in my repository. I will try to fix it in the next month. After the first release I will open a new issue here to mark this repository as deprecated and link to my fork. I'm new to github and opensource contribution, so I need time to adapt my wellknown processes. |
If I add a password protected zip file in the application package, I get the following error with version 1.8.6 :
The error is not present in version 1.7.X
I think the cause is the pull request #206 (comment)
I'm wondering if usage of zip files as resource, should be configurable, using a switch in getdown.txt file ? This would also close #275
The text was updated successfully, but these errors were encountered: