Ability to match "entry"/ "root" process name dynamically when using ENHANCER_CONFIG_FILE

[adamscybot]

At the moment, the rule system needs static process name matching.

However, the need to specify the process name is overly burdensome if you have a simple binary that you want to run ad-hoc with the ENHANCER_CONFIG_FILE env var inline (and LD_PRELOAD, in my case), because you don't really care about the process name, as it's implied by the call itself.

I would suggest there could be something like an %root% token that can be used in place of the process name:

program %root%
{
  ...
}

This would also be powerful in that you could have generic conf files that you can use with multiple binaries like this.

I realise if you then used this in a mode where LD_PRELOAD hooked everything, this would cause an extremity of hooks on every process, and that's not the use case for this (though, I guess it would do what they asked for if someone tried). Could be limited to only when passed via ENHANCER_CONFIG_FILE or something.

I guess this touches on a wider, less scoped use case about allowing interpolation from env vars as an alternative, though I realise allowing substitution, anywhere in the rule would probably open a bigger scary security minefield when we're already standing in one by using LD_PRELOAD in the first place. But perhaps that's just opening an unnecessarily large can of worms.

[ColumPaget]

I'm a bit worried about trying this, as it could mean that enhancer rules would get applied to the wrong processes, but I'll have a think about this and see if I can come up with something.

[ColumPaget]

I think I see what you're getting at here. As one can name the config files to a process name, it's redundant to require the process name to be specified within the file. I need to think on this one for a bit.