During debugging I noticed the safari warning:
AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.
After some research, I discovered that AES-GCM is widely recommended for its built-in authentication mechanism, which helps protect against chosen-ciphertext attacks. This pull request updates our encryption method from AES-CBC/AES-CTR to AES-GCM to address this vulnerability and ensure better security.
During debugging I noticed the safari warning:
AES-CBC and AES-CTR do not provide authentication by default, and implementing it manually can result in minor, but serious mistakes. We recommended using authenticated encryption like AES-GCM to protect against chosen-ciphertext attacks.After some research, I discovered that AES-GCM is widely recommended for its built-in authentication mechanism, which helps protect against chosen-ciphertext attacks. This pull request updates our encryption method from AES-CBC/AES-CTR to AES-GCM to address this vulnerability and ensure better security.