After the discussion here about sensitive data, mostly because of usefully comments by David and John, I ended coming to the conclusion I need to spend a week or two or so on a little side project to create a simple vault for my DSL to use.
I'm writing two tiny fuse filesystems that can give any "executable running as user" combo its own little vault.
For a native binary this is trivial even if it requires some extra privsep work because /proc/$PID/atte/current and /proc/$PID/exe van be trusted. The same is however not true for /proc/$PID/cmdline , because argv is mutable.
There are workarounds for this, but these are specific for specific VMs or interpreters and those require MAC (AppArmor or SeLinux) configurations to work, what all isn't too user friendly and is frankly too much work for a quick side project.
Because in Merg-E, when not compiled (first runtime won't be), argv isn't mutable for "scripts", it is defendable to allow my mini filesystem to trust /proc/$PID/cmdline to not be spoofed.
Even if I'm making this side project only to scratch my own itch for Merg-E, it would be great if I wouldn't close the door on other interpreters or on VMs that are also not vulnerable to argv spoofing.
I'm guessing Typhon would very likely not be vulnerable, but I still know too little about Monte and Typhon to be sure. And I'm interested to learn if there are any other interpreters or VMs that fit the bill.
If there are, I'd like to (for now) hard code these into my vault.