Enforce encrypted zip for unstreaming when password parameter is supplied #96
Closed
HugoMichelCognex
started this conversation in
Ideas
Replies: 1 comment 6 replies
-
It should be possible yes. And in fact I wonder if this should be the default behaviour, and maybe even not turn-offable... it'll be technically a backwards-incompatible change, but I suspect that's fine. For a bit of background, what sort of encryption do your zip files use? Old-style ZipCrypto or AES? (And if AES, what key length encryption key if you know?) |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey,
I just found out using your library (which is really nice btw, thank you very much) that even if you specify a password in the
stream_unzip
method, you can still send zip that are not encrypted and they are still being read.While this can be a nice feature, it could also be a problem if you want to control the input zip that is being passed. In our case, we want to be sure the input zip has been produced by us and is therefore encrypted with our password.
Could it be possible to add either an option or a flag to raise an error if you try to read a non-encrypted archive when you supply a password? I have not fully read your code, but this should (?) be possible I guess.
Thanks 🙏
Beta Was this translation helpful? Give feedback.
All reactions