m-chrzan.xyz
aboutsummaryrefslogtreecommitdiff
path: root/tests/gnupg/private-keys-v1.d/615FC2A5B2CBFD58B7FFA0A140D43B74AB9748B0.key
diff options
context:
space:
mode:
authorguns <self@sungpae.com>2012-10-16 17:28:15 -0500
committerJason A. Donenfeld <Jason@zx2c4.com>2012-10-17 00:53:50 +0200
commit8c46958d559d6fbb852f341f0fc2d5d60127ed91 (patch)
treec54c00eb0a4d2be174cccc629ee222b759aa2a29 /tests/gnupg/private-keys-v1.d/615FC2A5B2CBFD58B7FFA0A140D43B74AB9748B0.key
parentde5282d1a6b17cd62122084e06eaaac36716a2c8 (diff)
Do not interpret backslashes when reading passwords
The `read` builtin accepts backslash notation for common non-printing characters by default, like `\t` and `\n`. This requires that any literal backslashes must also be escaped as `\\`. Given that `gpg -e` does not interpret input, the `read` invocations are changed to do the same. Also, the right hand side of an `==` comparison within `[[ ]]` must be quoted in order to suppress pattern metacharacter expansion. Quoting the bash manual: When the == and != operators are used, the string to the right of the operator is considered a pattern and matched according to the rules described below under Pattern Matching.
Diffstat (limited to 'tests/gnupg/private-keys-v1.d/615FC2A5B2CBFD58B7FFA0A140D43B74AB9748B0.key')
0 files changed, 0 insertions, 0 deletions