-
Notifications
You must be signed in to change notification settings - Fork 71
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
Add support for AES in EncryptionService #365
Comments
major change. Otherwise EncryptionService and StringEncrypter are internal parts of the project and they can be used in such ways for encrypting various strings, not only for Encrypting Ldap Password. There are some ways for implementing AES support, including solving Symmetric Key:
The main discussion questions:
|
I think we need to replace deprecated 3DS with AES. We use this service to protect passwords in configuration files. We don't use it to protect data which we send over network. Hence this approach should be simple to allow implement it in Python/JS too. |
I think @yurem is advocating for salt. If AES is sufficient today, let's keep it simple. |
Why this Issue has status "To Be Assigned" ? It's implemented but not merged yet: |
@shmorri |
jgomer2001 commented on Mar 9, 2020
Currently we support 3DES as cipher, usage will be considered disallowed after 2023.
See https://www.cryptomathic.com/news-events/blog/3des-is-officially-being-retired
The text was updated successfully, but these errors were encountered: