Run unknown shell script with a line-by-line confirmation prompt

I want this to run my own shell scripts. I have a bunch of scripts that are halfway between "documentation" and "automation"; mostly the record of the last time I did X. Add a…

> I want this to run my own shell scripts. That's really the only use case for this tool that I could get behind, and I commend you for your diligence.

> Useful for running unknown scripts Or just, you know, read them before you run them.

If you are considering using this tool, then I would suggest that you seriously reevaluate your life choices. You should never run shell scripts without reading them first, ever.…

I understand your point, but there is a big difference between running a 20 year old program written in C and running a shell script that someone with one or two years of…

You can fool it with ^H (Insert with ^V^H in vim) ``` #!/bin/sh rm not ^H^H^H^H expected ``` Gives: ``` -> rm expected Run command? [Y/n] rm: cannot remove 'not': No such file or…

Heredocs are a little odd, because you can't see what they might be piping to. This script, for example looks sort of innocuous when run through your tool because it's not…

Very difficult to do in any kind of robust way. A script can run all kinds of things and use myriad forms of obfuscation, causing all kinds of obscure side effects.

In its full generality this runs afoul of the halting problem. That doesn't mean what you want is completely unattainable, you just need to figure out whether you're okay with…

If you are happy with running it only once in the container, yes. But if you run it first in the container to see whether is does anything bad and then run it on the host (or a…

What would be amazing is a tool that analyses the script first, figures out folders and files (and networking) it influences and allows to sandbox it accordingly. This script…

I would be fine with a static analyser doing the last one (giving up in doubt), considering that install scripts are a smaller subset of all possible shell scripts. Such a static…

I imagine this could be done by actually running the script in some sort of sandbox, having file changes written to overlayfs at first. This would still allow the script to steal…

You could do this by running your script pivot mounted into a namespace that mounts your "real" filesystem as readonly and layers with overlayfs to log changes. You can then…

Can I use it to run itself?

You can also do this with bashdb which is possibly also a more robust solution.

This is exactly what deno is useful for. Write your script in typescript and then run it with deno --prompt. I made a little demonstration script. ``` deno run --prompt…

Possibly relevant, the bash restricted shell (bash -r): https://www.gnu.org/software/bash/manual/html_node/The-Restricted-Shell.html

That sounds a lot like what maybe[1] does. [1] https://github.com/p-e-w/maybe