It looks like Microsoft's documentation suggests it will only work on older versions of Windows. From the README:
> Indeed, for what I've tested, under Windows 10, CryptReleaseContext does cleanup the memory (and so this recovery technique won't work). It can work under Windows XP because, in this version, CryptReleaseContext does not do the cleanup. Moreover, MSDN states this, for this function : "After this function is called, the released CSP handle is no longer valid. This function does not destroy key containers or key pairs.". So, it seems that there are no clean and cross-platform ways under Windows to clean this memory.
I'd be curious where the change happened between XP and 10.
This quote from the article indicates the opposite effect, actually! I'd like to see the study that concluded this, but it's an easy statement for me to believe.
> "As for connecting marijuana to the legal opioid crisis, Spicer has it exactly backwards. Greater access to marijuana has actually led to declines in opioid use, overdoses and other problems."
He doesn't listen to experts or research. Instead, he uses common sense.
“So really,” continued Eric, “I should be saying sorry to you, for jumping to the wrong conclusion. Instead of considering all the evidence, I just applied some common sense—otherwise known as prejudice—and came up with a totally wrong answer.”
― Lucy Hawking, George's Secret Key to the Universe
Another benefit of the Nexus program is that it's trivial to achieve root, so you can easily get to the point of removing even the small amount of bundled crapware.
My company, my family, and my friends all use Voxer for this. It's a great free push-to-talk style chat app, and we love the hybrid a/synchronous model of communication.
As someone mentioned below, Google Voice can do this natively if you press a button during a call. It alerts the person on the other end of the line and makes a recording available in your account following the call. Quite useful and works on any phone provided you're using GV.
> Indeed, for what I've tested, under Windows 10, CryptReleaseContext does cleanup the memory (and so this recovery technique won't work). It can work under Windows XP because, in this version, CryptReleaseContext does not do the cleanup. Moreover, MSDN states this, for this function : "After this function is called, the released CSP handle is no longer valid. This function does not destroy key containers or key pairs.". So, it seems that there are no clean and cross-platform ways under Windows to clean this memory.
I'd be curious where the change happened between XP and 10.