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
{{ message }}
This repository has been archived by the owner on May 23, 2022. It is now read-only.
Hi David,
Thanks for a great project; I've been using it for about 18 months in a modified form.
I wondered if you had any thoughts on content visibility in a process memory dump; Some of my files are visible (in plain text) in 2 or three locations in a memory dump :(.
Obfusication would help a bit, but my project does not do well with uglify-js.
I was thinking to memory map the file, and decrypt 'on the fly' during require, and scrub then force GC of the decrypted buffer after compilation just to minimise the available plain text (and also to minimise memory footprint of loaded prcoess).
Ideas?
s
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi David,
Thanks for a great project; I've been using it for about 18 months in a modified form.
I wondered if you had any thoughts on content visibility in a process memory dump; Some of my files are visible (in plain text) in 2 or three locations in a memory dump :(.
Obfusication would help a bit, but my project does not do well with uglify-js.
I was thinking to memory map the file, and decrypt 'on the fly' during require, and scrub then force GC of the decrypted buffer after compilation just to minimise the available plain text (and also to minimise memory footprint of loaded prcoess).
Ideas?
s
The text was updated successfully, but these errors were encountered: