-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Get rid of openssl_seal in encryption code #2182
Comments
agreed. 👍 Please keep backward compatibility in mind. |
I would suggest to make this changes in a new encryption module, there are some other stuff we can improve as well. The advantage of doing this in a second encryption module is that backward compatibility is easy and we don't face any limitations because of backward compatibility for the new module: |
Ok. Good point. Let's take a look at that for 12. Going this approach we should take the less error-prone approach and use the OpenSSL AEAD support in PHP 7.1. So basically a new encryption module that requires at least PHP 7.1. I checked with @oparoz on that and this would be ok for this customer. |
See also #20146 (comment) |
Getting rid of RC4 isn't dependent on replacing With #35916 I introduced |
Preparations have been done in #36173. |
Implemented in #37243. |
We should get rid of openssl_seal in the encryption app as that uses the RC4 cipher which considered out-of-date. At the moment it is used for encrypting multi-keys to file recipients.
We should replace the
openssl_seal
part with an approach usingopenssl_public_encrypt
(OPENSSL_PKCS1_OAEP_PADDING
).cc @schiessle @oparoz @karlitschek
The text was updated successfully, but these errors were encountered: