-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
[FEATURE]Security Question #25
Comments
In addition, this is a crash log during encryption and compression. When entering the password and clicking compression, a crash occurred. |
Did you select compression method - AES_INTERNAL_ONLY ? If yes I actually got that issue before but forgot to removed that parameter. |
Yeah, it can be removed or maybe not completely removed, but a warning that it is not safe to use, remove from the default method.
Yeah, Sure.
Maybe, I am not sure about this, will see what can be done. |
Yes, I retried the deflate compression algorithm and it worked successfully. |
grateful! Looking forward to what happens next. |
Sorry, I may have confused you. There may be a problem with the translation software. I mean can you provide/add AES128GCM, AES192GCM, AES256GCM options in future versions. |
Ooh, Ok. It will be added 👍 |
The Zip standard encryption method has been proven to be no longer safe and has broken weaknesses more than ten years ago. It is recommended to remove this encryption algorithm. For AES encryption, can I add aes128gcm, aes192gcm, and aes256gcm to choose from? Can ChaCha20-Poly1305/XChaCha20-Poly1305 be added to devices with weak performance? Or AEGIS256/128L etc. (libsodium)
The text was updated successfully, but these errors were encountered: