1. 06 Dec, 2018 1 commit
    • Milan Broz's avatar
      Add crypt_set_data_offset API function. · 03edcd2b
      Milan Broz authored
      The crypt_set_data_offset sets the data offset for LUKS and LUKS2 devices
      to specified value in 512-byte sectors.
      
      This value should replace alignment calculation in LUKS param structures.
      03edcd2b
  2. 27 Oct, 2018 1 commit
  3. 08 Aug, 2018 1 commit
  4. 06 Aug, 2018 1 commit
    • Milan Broz's avatar
      Use only xz archives in tests. · e53fe706
      Milan Broz authored
      Bzip2 is sometimesmissing and we use xz already.
      
      Seems xz produces slightly larger archives (despite the best mode)
      but it is not worth to keep bz2 here.
      e53fe706
  5. 21 Jul, 2018 1 commit
  6. 18 Jul, 2018 1 commit
  7. 13 Jul, 2018 1 commit
  8. 07 Jul, 2018 1 commit
  9. 25 Apr, 2018 1 commit
  10. 19 Apr, 2018 1 commit
  11. 15 Apr, 2018 1 commit
  12. 25 Mar, 2018 1 commit
  13. 23 Mar, 2018 1 commit
  14. 01 Mar, 2018 1 commit
  15. 17 Jan, 2018 1 commit
    • Milan Broz's avatar
      Introduce new 64bit *keyfile_device_offset functions. · f34ce81f
      Milan Broz authored
      The keyfile interface was designed, well, for keyfiles.
      
      Unfortunately, a keyfile can be placed on a device and the size_t offset
      can overflow.
      
      We have to introduce new set of fucntions that allows 64bit offsets even on 32bit systems:
       - crypt_resume_by_keyfile_device_offset
       - crypt_keyslot_add_by_keyfile_device_offset
       - crypt_activate_by_keyfile_device_offset
       - crypt_keyfile_device_read
      
      The new functions have added _device_ in name.
      
      Old functions are just internall wrappers around these.
      
      Also cryptsetup --keyfile-offset and --new-keyfile-offset must now
      process 64bit offsets.
      
      For more info see issue 359.
      f34ce81f
  16. 10 Dec, 2017 1 commit
    • Milan Broz's avatar
      Fix a rare fail in key-length regression test with PBKDF2. · f049afcb
      Milan Broz authored
      PBKDF2 has nasty behaviour that it generates the same output
      for passwords that has several trailing zero bytes.
      (IOW null trailing bytes causes collision.)
      
      Unfortunatelly our test plays with password length
      and expect wrong length must always fail.
      Sometimes the randomly generated key key contains
      the null byte in the "wrong" place and PBKDF2 causes test to fail.
      
      For now, fix it by using fixed keyfile without null bytes
      (similar to fixed passphrased we already have).
      f049afcb
  17. 07 Dec, 2017 1 commit
  18. 12 Oct, 2017 1 commit
    • Milan Broz's avatar
      Use non-recursive automake. · d77bbe93
      Milan Broz authored
      This change also causes that now binaries and libraries are placed in
      build root directory.
      
      Now we can use subdir-objects for automake.
      d77bbe93
  19. 10 Oct, 2017 1 commit
  20. 04 Oct, 2017 1 commit
  21. 24 Sep, 2017 2 commits
  22. 23 Aug, 2017 1 commit
  23. 10 Aug, 2017 2 commits
  24. 07 Aug, 2017 1 commit
  25. 27 Jun, 2017 2 commits
  26. 24 Jun, 2017 4 commits
  27. 21 Jun, 2017 1 commit
  28. 01 Jan, 2016 1 commit
  29. 22 Nov, 2015 1 commit
  30. 29 Oct, 2015 1 commit
  31. 26 Aug, 2015 1 commit
  32. 19 Aug, 2015 1 commit
  33. 26 Jan, 2015 2 commits