Change Details

We are aware of memory leaks using the `new` allocation for the cryptoPP classes and used unique pointers and `release()`. Acording to the CryptoPP pipeline documentation we don't need to free memory manualy and can switch to the `new` approach because using unique pointers and `release()` have no makes sense here. Related linear task: ENG-627

We are aware of memory leaks using the `new` allocation for the cryptoPP classes and used unique pointers and `release()`. According to the [[ https://cryptopp.com/wiki/Pipelining#Ownership | CryptoPP pipeline documentation ]], we don't need to free the memory manually and can switch to the `new` approach because using unique pointers and `release()` have no makes sense here. Related linear task: [[ https://linear.app/comm/issue/ENG-627/investigate-cryptopp-pointers-memory-release-in-tunnelbroker | ENG-627 ]]

We are aware of memory leaks using the `new` allocation for the cryptoPP classes and used unique pointers and `release()`. AcAccording to thehe [[ https://cryptopp.com/wiki/Pipelining#Ownership | CryptoPP pipeline documentation ]], we don't need to free the memory manualylly and can switch to the `new` approach because using unique pointers and `release()` have no makes sense here. Related linear task: [[ https://linear.app/comm/issue/ENG-627/investigate-cryptopp-pointers-memory-release-in-tunnelbroker | ENG-627 ]]