1. 20 Jan, 2017 2 commits
  2. 05 Jan, 2017 1 commit
  3. 13 Dec, 2016 1 commit
  4. 03 Nov, 2016 1 commit
  5. 22 Oct, 2016 1 commit
  6. 21 Oct, 2016 1 commit
    • Jonas Meurer's avatar
      Fix several minor spelling errors found by Lintian · b2a6e338
      Jonas Meurer authored
      * lib/setup.c: miliseconds -> milliseconds
      * lib/utils_wipe.c: Unsuported -> Unsupported
      * man/crypsetup.8: implicitely -> implicitly
      * man/veritysetup.8: verion -> version
      * python/pycryptsetup.c: miliseconds -> milliseconds
      b2a6e338
  7. 20 Oct, 2016 2 commits
  8. 19 Oct, 2016 2 commits
  9. 18 Oct, 2016 1 commit
  10. 02 Jul, 2016 3 commits
  11. 23 Jun, 2016 1 commit
  12. 08 Jun, 2016 1 commit
    • Ondrej Kozina's avatar
      code cleanup related to devfd checks · 16fab74a
      Ondrej Kozina authored
      alter all checks for devfd value after device_open to
      less than zero insted of equals to -1. device_open will
      return values different from -1 in case error happens.
      
      In LUKSv1 device_open should always return -1 in case of
      error but this check is safer.
      
      The rest is just formating improvement.
      16fab74a
  13. 13 May, 2016 1 commit
    • Ondrej Kozina's avatar
      keymanage: eliminate double close() call · e1dca468
      Ondrej Kozina authored
      fix  double close() cases in LUKS_hdr_backup() and LUKS_hdr_restore()
      functions. It should be harmless unless libcryptsetup is used
      in multi-thread setup which is not supported anyway.
      e1dca468
  14. 04 May, 2016 1 commit
    • Milan Broz's avatar
      Support activation options for error handling modes in dm-verity. · 4dd703ea
      Milan Broz authored
      This patch adds veritysetup support for these Linux kernel dm-verity options:
      
        --ignore-corruption - dm-verity just logs detected corruption
        --restart-on-corruption - dm-verity restarts the kernel if corruption is detected
      
        If the options above are not specified, default behaviour for dm-verity remains.
        Default is that I/O operation fails with I/O error if corrupted block is detected.
      
        --ignore-zero-blocks - Instructs dm-verity to not verify blocks that are expected
         to contain zeroes and always return zeroes directly instead.
      
      NOTE that these options could have serious security or functional impacts,
      do not use them without assessing the risks!
      4dd703ea
  15. 24 Apr, 2016 2 commits
    • Milan Broz's avatar
      Avoid possible divide-by-zero warnings. · 7eba57b4
      Milan Broz authored
      7eba57b4
    • Milan Broz's avatar
      Fix warnings reported by static analysis. · 683e4db4
      Milan Broz authored
      - ensure that strings are \0 terminated (most of this is already
      handled on higher level anyway)
      
      - fix resource leak in error path in tcrypt.c
      
      - fix time of check/time of use race in sysfs path processing
      
      - insruct Coverity scanner to ignore constant expression in random.c
      (it is intented to stop compile-time misconfiguration of RNG that would be fatal)
      683e4db4
  16. 19 Apr, 2016 2 commits
  17. 23 Mar, 2016 1 commit
  18. 19 Mar, 2016 1 commit
    • athira-rajeev's avatar
      Fix device_block_size_fd to return bsize correctly incase of files. · 8e4e898c
      athira-rajeev authored
      This patch is for issue #287
      
      In the code for returning block size ( device_block_size_fd in lib/utils_device.c ),
      always returns zero in case of files and device_read_test is not executed.
      
      This patch is to fix device_block_size_fd to return block size correctly incase of files.
      
      Signed-off-by: Athira Rajeevatrajeev@linux.vnet.ibm.com
      8e4e898c
  19. 04 Jan, 2016 1 commit
  20. 03 Jan, 2016 2 commits
  21. 02 Jan, 2016 2 commits
  22. 12 Dec, 2015 1 commit
  23. 01 Dec, 2015 6 commits
  24. 20 Nov, 2015 3 commits