best practice when spawning commands that require sudo?
I am building a command line utility in deno that leverages data coming from
Im not sure if I have a suggestion yet on how we could improve this. Right now I am just curious if anyone else has ran into this. I could leverage roles & permissions on my linux machine to allow this program to run without sudo, but thats not very portable, other users would have to do the same "add user/allow user access to x,y,z/change user to run the command/etc"
tcpdumptcpdump. To get any meaningful data out of tcpdumptcpdump, I need elevated permissions. To keep this command portable, that means running sudo tcpdumpsudo tcpdump inside my deno program. How can I set up deno permissions to run a specific command executed through sudosudo? A simple permission of --allow-run=sudo--allow-run=sudo would be dangerous. I could just let the user approve each time, but even then, all they know is that they are approving sudosudo, there is no other knowledge of what the subcommand is:Im not sure if I have a suggestion yet on how we could improve this. Right now I am just curious if anyone else has ran into this. I could leverage roles & permissions on my linux machine to allow this program to run without sudo, but thats not very portable, other users would have to do the same "add user/allow user access to x,y,z/change user to run the command/etc"
