How to deal with interpreters? #606
Unanswered
martin-braun
asked this question in
Q&A
Replies: 2 comments
-
Beta Was this translation helpful? Give feedback.
0 replies
-
Yes this would be good to have! I think the "easiest" option would be to have a rule option (for interpreters) that would allow you to create a rule for the interpreter + script (some what how now you can create a rule that is for process + endpoint). So you could make a rule for: Thoughts? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I stopped using Little Snitch and want to use Lulu. The experience is great, so thanks for the good product.
One thing that I miss though are rules that are defined based on the host who spawned the process in question.
For instance. An application, written in Java, will spawn the Java binary in the rule setup of Lulu. If two Applications are Java applications, their rules have to be shared, since those are Java rules, not specific Application rules.
The same limitation is present with other interpreters, such as Deno, Python, node, etc.
Little Snitch allowed rules to be different based on the caller. So much so, that I could even influence
curl
rules for each script individually.Can something like this be done in Lulu already? Or is it planned?
EDIT: I just see that the
java
rule is in fact for a binary embedded into the Application, so this might not be a problem. Still, I think this would be such a great addition.Beta Was this translation helpful? Give feedback.
All reactions