Closed lionelains closed 4 years ago
When grabbing an AES object to perform AES computation, today, we return a pointer. This leads to a memory leak (object is never de-allocated). Instead, we should return a std::unique_ptr
std::unique_ptr
Using std::unique_ptr is no compatible with the support of DYNAMIC_ALLOCATION
DYNAMIC_ALLOCATION
Fixed by 187243d77738ce525cdad7343b1ff2d02a35c556
When grabbing an AES object to perform AES computation, today, we return a pointer. This leads to a memory leak (object is never de-allocated). Instead, we should return a
std::unique_ptr