diff options
| author | guns <self@sungpae.com> | 2012-10-16 17:28:15 -0500 |
|---|---|---|
| committer | Jason A. Donenfeld <Jason@zx2c4.com> | 2012-10-17 00:53:50 +0200 |
| commit | 8c46958d559d6fbb852f341f0fc2d5d60127ed91 (patch) | |
| tree | c54c00eb0a4d2be174cccc629ee222b759aa2a29 /contrib | |
| parent | de5282d1a6b17cd62122084e06eaaac36716a2c8 (diff) | |
| download | pass-8c46958d559d6fbb852f341f0fc2d5d60127ed91.tar.gz pass-8c46958d559d6fbb852f341f0fc2d5d60127ed91.tar.bz2 pass-8c46958d559d6fbb852f341f0fc2d5d60127ed91.zip | |
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 'contrib')
0 files changed, 0 insertions, 0 deletions