hermes - 💡(How to fix) Fix [Security/Enhancement] AES-256-GCM Nonce Reuse Risk in Local Long-Term Memory Updates

Overview: Upon reviewing the forced local AES-256-GCM encryption mechanism for the Long-Term Memory (LTM) module, there is a critical architectural risk regarding how Initialization Vectors (IVs) / Nonces are managed during recurrent memory file updates.

Details: AES-GCM fundamentally relies on unique Nonces for every encryption operation. In local LTM implementations where the same memory file is frequently appended to or overwritten, there is a high likelihood of Nonce/IV reuse if the entropy source or counter mechanism is not properly stateful across sessions or process restarts.

Suggested Solution: Ensure a robust Nonce management system. Consider using random 96-bit nonces generated from a CSPRNG for every single write operation to the LTM file, ensuring that the same key-nonce pair is never used twice, thereby preserving AES-GCM's authentication and confidentiality guarantees.

Impact: Prevents catastrophic compromise of the AES-GCM security model and leakage of sensitive agent context.