-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make parameter passing to shell scripts secure #7
Comments
In this example, I'd make sure that repository can only be a valid path/directory (allowed chars are |
Good programming languages usually have something like As there is no shell involved the is not "command parsing", "string escaping" etc. |
@jgraichen but that still would be exploitable if not used very carefully, right? |
No. Something like |
Passing the responsibility to the target command is probably a good idea here. And yes, it looks like |
but.. since the target programming is a shell script that we wrote... e.g. lively4sync than we have to deal with the security ourselves there again.... some of the commands are not just direct calls to the git api. |
Rewrite the shell script in JS? ;) |
if it would have been easy to write in JS I would not have needed a shell script ;-) |
but for some git commands, I see that this is the most secure option... |
let's have a look at this next monday! |
Tim sagt du sollst JETZT Wochenende machen.... |
Tim ist d##f 😉 ...selber Wochenende! |
Is there an accepted general way to pass parameters to the scripts securely? I just stripping our ' enough?
The text was updated successfully, but these errors were encountered: