On Tuesday, January 3, 2017 at 11:41:44 PM UTC-5, c++programmer wrote:
>
> I've been having an issue where decrypted data is left in RAM once I'm
> done with it. I've traced the problem to decrypting the data to a
> std::string. So I've started to move all my code over to use SecByteBlock.
>
By the way, something else you can do is:
typedef std::basic_string<char, std::char_traits<char>,
AllocatorWithCleanup<char> > secure_string;
Jeff
--
--
You received this message because you are subscribed to the "Crypto++ Users"
Google Group.
To unsubscribe, send an email to cryptopp-users-unsubscr...@googlegroups.com.
More information about Crypto++ and this group is available at
http://www.cryptopp.com.
---
You received this message because you are subscribed to the Google Groups
"Crypto++ Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to cryptopp-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
