ChatGPT解决这个技术问题 Extra ChatGPT

Escape a string for a sed replace pattern

In my bash script I have an external (received from user) string, which I should use in sed pattern.

REPLACE="<funny characters here>"
sed "s/KEYWORD/$REPLACE/g"

How can I escape the $REPLACE string so it would be safely accepted by sed as a literal replacement?

NOTE: The KEYWORD is a dumb substring with no matches etc. It is not supplied by user.

Are you trying to avoid the "Little Bobby Tables" problem if they say "/g -e 's/PASSWORD=.*/PASSWORD=abc/g'"?
If using bash, you don't need sed. Just use outputvar="${inputvar//"$txt2replace"/"$txt2replacewith"}".
@destenson I think you shouldn't be putting the two variables outside the quotes. Bash can read variables inside double-quotes (in your example, whitespace could screw things up).
@CamiloMartin, see my comment on my own answer. The quotes inside of the ${} do not match up with the quotes inside. The two variables are not outside the quotes.

C
Cadoiz

Warning: This does not consider newlines. For a more in-depth answer, see this SO-question instead. (Thanks, Ed Morton & Niklas Peter)

Note that escaping everything is a bad idea. Sed needs many characters to be escaped to get their special meaning. For example, if you escape a digit in the replacement string, it will turn in to a backreference.

As Ben Blank said, there are only three characters that need to be escaped in the replacement string (escapes themselves, forward slash for end of statement and & for replace all):

ESCAPED_REPLACE=$(printf '%s\n' "$REPLACE" | sed -e 's/[\/&]/\\&/g')
# Now you can use ESCAPED_REPLACE in the original sed statement
sed "s/KEYWORD/$ESCAPED_REPLACE/g"

If you ever need to escape the KEYWORD string, the following is the one you need:

sed -e 's/[]\/$*.^[]/\\&/g'

And can be used by:

KEYWORD="The Keyword You Need";
ESCAPED_KEYWORD=$(printf '%s\n' "$KEYWORD" | sed -e 's/[]\/$*.^[]/\\&/g');

# Now you can use it inside the original sed statement to replace text
sed "s/$ESCAPED_KEYWORD/$ESCAPED_REPLACE/g"

Remember, if you use a character other than / as delimiter, you need replace the slash in the expressions above wih the character you are using. See PeterJCLaw's comment for explanation.

Edited: Due to some corner cases previously not accounted for, the commands above have changed several times. Check the edit history for details.


It's worth noting that you can avoid having to escape the forward slashes by not using them as the delimiters. Most (all?) versions of sed allow you to use any character, so long as it fits the pattern: $ echo 'foo/bar' | sed s_/_:_ # foo:bar
@PeterJCLaw: Good point. I believe that is true for all versions of sed. There are only two escaped slashes above, so it wouldn't make much difference, but it matters if you use another delimiter in the sed expression this output is inserted into. I added some info to reflect that.
a
a_horse_with_no_name

The sed command allows you to use other characters instead of / as separator:

sed 's#"http://www\.fubar\.com"#URL_FUBAR#g'

The double quotes are not a problem.


You still need to escape . which otherwise has a special meaning. I edited your answer.
I have just tried to do : sed '/CLIENTSCRIPT="foo"/a CLIENTSCRIPT2="hello"' file with sed '|CLIENTSCRIPT="foo"|a CLIENTSCRIPT2="hello"' file and that does not do the same.
Because this applies only to substitute, this should be saying: The s command (as in substitute) of sed allows you to use other characters instead of / as a separator. Also, this would be an answer to how to use sed on URL with slash characters. It does not answer the OP question how to escape a string entered by a user, which could contain /, \, but also # if you decide to use that. And besides, URI can contain # too
M
Mark Stosberg

The only three literal characters which are treated specially in the replace clause are / (to close the clause), \ (to escape characters, backreference, &c.), and & (to include the match in the replacement). Therefore, all you need to do is escape those three characters:

sed "s/KEYWORD/$(echo $REPLACE | sed -e 's/\\/\\\\/g; s/\//\\\//g; s/&/\\\&/g')/g"

Example:

$ export REPLACE="'\"|\\/><&!"
$ echo fooKEYWORDbar | sed "s/KEYWORD/$(echo $REPLACE | sed -e 's/\\/\\\\/g; s/\//\\\//g; s/&/\\\&/g')/g"
foo'"|\/><&!bar

Also a newline, I think. How do I escape a newline?
Be careful what the default behavior of echo is with regard to backslashes. In bash, echo defaults to no interpretation of backslash escapes, which serves the purpose here. In dash (sh), on the other hand, echo interprets backslash escapes and has no way, as far as I know, of suppressing this. Therefore, in dash (sh), instead of echo $x, do printf '%s\n' $x.
Also, always use the -r option when doing a read to treat backslashes in user input as literals.
For cross-platform compatibility with other shells, you should consult this document regarding the replacement of sed special characters: grymoire.com/Unix/Sed.html#toc-uh-62
@Drux The three characters are the only special ones in the replace clause. Much more is special in the pattern clause.
G
Gurpartap Singh

Based on Pianosaurus's regular expressions, I made a bash function that escapes both keyword and replacement.

function sedeasy {
  sed -i "s/$(echo $1 | sed -e 's/\([[\/.*]\|\]\)/\\&/g')/$(echo $2 | sed -e 's/[\/&]/\\&/g')/g" $3
}

Here's how you use it:

sedeasy "include /etc/nginx/conf.d/*" "include /apps/*/conf/nginx.conf" /etc/nginx/nginx.conf

thanks! if anyone else gets syntax error when trying to use it, just like me, just remember to run it using bash, not sh
Is there a function just to escape a string for sed instead of wrapping around sed?
Hey, just a general warning regarding starting pipes with an echo like this: Some (most?) implementations of echo take options (see man echo), causing the pipe to behave unexpectedly when your argument $1 begins with a dash. Instead, you can start your pipe with printf '%s\n' "$1".
It doesn't work with new lines e.g. " sedeasy "hello world" "hello\n world" "x.txt"
f
fedorqui

It's a bit late to respond... but there IS a much simpler way to do this. Just change the delimiter (i.e., the character that separates fields). So, instead of s/foo/bar/ you write s|bar|foo.

And, here's the easy way to do this:

sed 's|/\*!50017 DEFINER=`snafu`@`localhost`\*/||g'

The resulting output is devoid of that nasty DEFINER clause.


No, & and `` must still be escaped, as must the delimiter, whichever is chosen.
That solved my problem, as I had "/" chars in a replacement string. Thanks, man!
works for me. What am doing is try to escape $ in the string about to be changed, and maintain the meaning of $ in the replacement string. say I want to change $XXX to the value of variable $YYY, sed -i "s|\$XXX|$YYY|g" file works fine.
D
Dennis Estenson

It turns out you're asking the wrong question. I also asked the wrong question. The reason it's wrong is the beginning of the first sentence: "In my bash script...".

I had the same question & made the same mistake. If you're using bash, you don't need to use sed to do string replacements (and it's much cleaner to use the replace feature built into bash).

Instead of something like, for example:

function escape-all-funny-characters() { UNKNOWN_CODE_THAT_ANSWERS_THE_QUESTION_YOU_ASKED; }
INPUT='some long string with KEYWORD that need replacing KEYWORD.'
A="$(escape-all-funny-characters 'KEYWORD')"
B="$(escape-all-funny-characters '<funny characters here>')"
OUTPUT="$(sed "s/$A/$B/g" <<<"$INPUT")"

you can use bash features exclusively:

INPUT='some long string with KEYWORD that need replacing KEYWORD.'
A='KEYWORD'
B='<funny characters here>'
OUTPUT="${INPUT//"$A"/"$B"}"

BTW, syntax highlighting here is wrong. The exterior quotes match up & the interior quotes match up. In other words, it looks like $A and $B are unquoted, but they are not. The quotes inside of the ${} do not match with the quotes outside of it.
You don't actually have to quote the right-hand side of an assignment (unless you want to do something like var='has space') – OUTPUT=${INPUT//"$A"/"$B"} is safe.
You don't actually have to quote the right-hand side of an assignment (unless you want it to work in the real world and not just as a toy script to show yur mad skilz). I always try to quote every variable expansion that I don't want the shell to interpret, unless I have a specific reason not to. That way, things tend to break less often, especially when when provided with new or unexpected input.
See manual: "All values undergo tilde expansion, parameter and variable expansion, command substitution, arithmetic expansion, and quote removal (detailed below)." I.e., the same as in double quotes.
What if you need to use sed on a file?
f
fedorqui

Use awk - it is cleaner:

$ awk -v R='//addr:\\file' '{ sub("THIS", R, $0); print $0 }' <<< "http://file:\_THIS_/path/to/a/file\\is\\\a\\ nightmare"
http://file:\_//addr:\file_/path/to/a/file\\is\\\a\\ nightmare

The trouble with awk is that it has nothing similar to sed -i, which comes extremely handy 99% of the time.
This is a step in the right direction, but awk still interprets some metacharacters in your substitution, so it's still not safe for user input.
A
Alex

Here is an example of an AWK I used a while ago. It is an AWK that prints new AWKS. AWK and SED being similar it may be a good template.

ls | awk '{ print "awk " "'"'"'"  " {print $1,$2,$3} " "'"'"'"  " " $1 ".old_ext > " $1 ".new_ext"  }' > for_the_birds

It looks excessive, but somehow that combination of quotes works to keep the ' printed as literals. Then if I remember correctly the vaiables are just surrounded with quotes like this: "$1". Try it, let me know how it works with SED.


A
Ark25

These are the escape codes that I've found:

* = \x2a
( = \x28
) = \x29

" = \x22
/ = \x2f
\ = \x5c

' = \x27
? = \x3f
% = \x25
^ = \x5e

Not all sed dialects accept hex escapes with \x. There's not much to "discover"; you can look up character codes in any ASCII chart.
N
NeronLeVelu

don't forget all the pleasure that occur with the shell limitation around " and '

so (in ksh)

Var=">New version of \"content' here <"
printf "%s" "${Var}" | sed "s/[&\/\\\\*\\"']/\\&/g' | read -r EscVar

echo "Here is your \"text\" to change" | sed "s/text/${EscVar}/g"

exactly the direction I was needed, for escaping find results, found through google so may be helpful for someone - ended with - sed "s/[&\\\*\\"\'\"' )(]/\\&/g'
M
Mark Stosberg

If the case happens to be that you are generating a random password to pass to sed replace pattern, then you choose to be careful about which set of characters in the random string. If you choose a password made by encoding a value as base64, then there is is only character that is both possible in base64 and is also a special character in sed replace pattern. That character is "/", and is easily removed from the password you are generating:

# password 32 characters log, minus any copies of the "/" character.
pass=`openssl rand -base64 32 | sed -e 's/\///g'`;

T
The Hungry Dictator

If you are just looking to replace Variable value in sed command then just remove Example:

sed -i 's/dev-/dev-$ENV/g' test to sed -i s/dev-/dev-$ENV/g test

A
Axel

I have an improvement over the sedeasy function, which WILL break with special characters like tab.

function sedeasy_improved {
    sed -i "s/$(
        echo "$1" | sed -e 's/\([[\/.*]\|\]\)/\\&/g' 
            | sed -e 's:\t:\\t:g'
    )/$(
        echo "$2" | sed -e 's/[\/&]/\\&/g' 
            | sed -e 's:\t:\\t:g'
    )/g" "$3"
}

So, whats different? $1 and $2 wrapped in quotes to avoid shell expansions and preserve tabs or double spaces.

Additional piping | sed -e 's:\t:\\t:g' (I like : as token) which transforms a tab in \t.


But see my comment on the sedeasy answer regarding using echo in pipes.
Piping sed to sed is just silly; a single sed instance can execute an arbitrarily long and complex script.
J
Javonne Martin

An easier way to do this is simply building the string before hand and using it as a parameter for sed

rpstring="s/KEYWORD/$REPLACE/g"
sed -i $rpstring  test.txt

Fails and extremely dangerous, as REPLACE is user supplied: REPLACE=/ gives sed: -e expression #1, char 12: unknown option to `s'