From 9b7c09b232ad6a92c7c45119807e4bac66dd7513 Mon Sep 17 00:00:00 2001 From: xenago Date: Fri, 22 Jul 2022 13:10:02 -0400 Subject: [PATCH] Update readme, build new release --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e793443..13b5c55 100755 --- a/README.md +++ b/README.md @@ -236,7 +236,7 @@ either empty JSON `{}` or nothing at all (other than whitespace/newlines) to `st Commands and arguments are split according to POSIX shell syntax, but are not run through a shell, so bash-specific syntax will not function. For example, a command such as `program1 && program2` will be interpreted as -running `program1` with arguments `&&` and `program2`. Although it is not recommended due to possible security risks, it +running `program1` with arguments `&&` and `program2`. Although it is not recommended (see the Security section), it remains possible to run a shell directly, e.g. `sh -c 'program1 && program2'`. Here is the expected JSON format from running each database's supported commands, with types indicated. All numbers are @@ -321,7 +321,7 @@ default. Ensure that this file, the commands defined inside it, and any other re inaccessible to any other users, or those users may be able to run commands as `root`. By default, commands are not passed through a shell for execution. Although it is possible to run commands like `bash` -with `libnss_shim`, using a shell is not recommended as this comes the risk of command injection. If a shell is still +with `libnss_shim`, using a shell is not recommended as this comes at the risk of command injection. If a shell is still used, the use of environment variables rather than arguments is critical. ## Useful resources