Skip to content
Snippets Groups Projects
  1. Mar 24, 2014
  2. Mar 23, 2014
  3. Mar 22, 2014
  4. Mar 20, 2014
  5. Mar 19, 2014
  6. Sep 14, 2013
  7. May 22, 2013
  8. Apr 04, 2013
  9. Feb 23, 2013
  10. Oct 18, 2012
  11. Oct 16, 2012
    • guns's avatar
      Do not interpret backslashes when reading passwords · 8c46958d
      guns authored
      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.
      8c46958d
  12. Oct 09, 2012
  13. Oct 05, 2012
  14. Oct 03, 2012
  15. Sep 30, 2012
  16. Sep 23, 2012
Loading