summaryrefslogtreecommitdiff
path: root/tests/gnupg/gpg.conf
blob: 60ece49b7f24f2a2cd10203213520b8a4ece0ec7 (plain)
1
2
3
group group1 = E4691410 D774A374
group group2 = E4691410
group big group = CF90C77B D774A374 EB7D54A8 E4691410 39E5020C
tr class='nohover-highlight'> 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. 2012-10-09Fix gpg22 man page typo.Jason A. Donenfeld1-1/+1 2012-10-09Restore exclusivity of options in multiline/echo check.Jason A. Donenfeld1-1/+1 2012-10-09Changes to lastpass2pass.rbAlex Sayers1-34/+27 - relicensed to GPLv2+ - added -f command-line flag - added -d DEFAULT_GROUP flag 2012-10-07Rename script internally and use generalized usage message filename.Jason A. Donenfeld1-2/+2