Adds a uint32 value to FileNode that is initialized to an
arbitrary value (CANARY_OK) in the constructor, and reset
when the reference is dropped (CANARY_RELEASED,
CANARY_DESTROYED).
The canary is checked on each withFileNode call.
Makes it much easier to trigger the bug seen in
https://github.com/vgough/encfs/issues/214 .
tinyxml2 does not support to read from a named pipe, since it uses seek to
figure out the file size. In the case of a pipe this is not possible.
Reading the file content into memory and passing the content to tinyxml2 allows
to mitigate this problem.
* Update cmake
* Update cmake, make Travis use it
* Enable all tests in a single command : make check
* Make cmake flawlessly run with Debian jessie cmake 3.0.2
* Make Travis use our own cmake 3.0.2 compiled version
* Typo in preferred version
* Be sure travis will have gettext
Currently the text displayed is
The directory "..." does not exist. Should it be created? (y,n)
This patch changes it to
The directory "..." does not exist. Should it be created? (y,N)
* Fix up encfssh
The original implementation of encfssh had several issues:
- Could not safely handle directory names with spaces
- Could not safely handle paths starting with a dash (`-`)
- Option strings could not be passed with spaces
- Could print incorrect help based on filenames in current directory
- Used `test` syntax deprecated in current POSIX.2 standard
- Had shell injection vulnerabilities based on both current working directory
and mount-point directory names.
- Failures of the canonicalize function could silently return the current
directory rather than the target.
In this version, shell injection is only permitted through the (explicitly
defined) `FUSE_UMOUNT` mechanism.
This version also adds support for the GNU-style "--help" argument.
The requirement that the password is not empty was not enforced
properly in all getUserKey() variants. Add the check to makeKey()
instead that is called in every code path.
This also fixes the crash desribed at https://github.com/vgough/encfs/issues/241 .
`$*` operates by:
- Concatenating all arguments with the first character in `IFS` (by default a space) into a single string
- Splitting that string on all characters found in `IFS` to join a list of words
- Expanding each of those words as a glob character
Thus, using `$*` in a wrapper means that an argument such as `"one word"` becomes two arguments, `one` and `word`, and an argument `'*.txt'` can be replaced with an entirely unknown number of arguments (`one.txt`, `two.txt`) despite its quoting.
Use `"$@"` to pass an argument vector through literally without any kind of expansion.
