You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the debugging of my encryption plugin, I identified an unnecessary reload of the encryption plugin in CryptoManager::lockAndReadHeader() (CryptoManager.cpp) for the Super architecture. This reload was unintentionally introduced by me in PR #7423. It can result in the plugin's key being overwritten during its operation, as occurred in my case.
This issue is primarily related to the specific implementation of my plugin and should not affect other plugins if they securely manage their keys and prevent spontaneous changes during encryption or decryption processes. However, for the Super architecture, this reload is redundant—it simply reloads the same plugin with the same key, serving no useful purpose. For this reason, I have decided to address it.
The reload is only required for the Classic architecture when the encryption state is modified from another process after an AST trigger.
This issue affects all major versions: 3, 4, 5, and 6. A PR with the fix will be provided shortly.
The text was updated successfully, but these errors were encountered:
Hello, colleagues,
During the debugging of my encryption plugin, I identified an unnecessary reload of the encryption plugin in
CryptoManager::lockAndReadHeader()
(CryptoManager.cpp) for the Super architecture. This reload was unintentionally introduced by me in PR #7423. It can result in the plugin's key being overwritten during its operation, as occurred in my case.This issue is primarily related to the specific implementation of my plugin and should not affect other plugins if they securely manage their keys and prevent spontaneous changes during encryption or decryption processes. However, for the Super architecture, this reload is redundant—it simply reloads the same plugin with the same key, serving no useful purpose. For this reason, I have decided to address it.
The reload is only required for the Classic architecture when the encryption state is modified from another process after an AST trigger.
This issue affects all major versions: 3, 4, 5, and 6. A PR with the fix will be provided shortly.
The text was updated successfully, but these errors were encountered: