You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wish I could write the proper article to explain the details. But lately I don't have much time.
Basically, when Molly get locked:
Clears the database encryption keys from memory
Kills the JVM and restart itself
Runs the WipeMemoryService in the background
Then the wipe service allocates large chunks of memory and overwrites them with random data, until there is no more free RAM available in the device. Then it frees everything and finalize. It takes a few seconds to complete, and you can see a notification and the progress bar.
All of this is to prevent forensic RAM analysis after Molly is locked. It's somehow a workaround to the known issue of JVM apps to overwrite its own memory.
Based on my understanding, it is used to overwrite values in app memory.
Why it's done? Security issue? is there any POC for that?
The text was updated successfully, but these errors were encountered: