1. 08 Feb, 2018 2 commits
  2. 20 Jan, 2018 4 commits
  3. 19 Jan, 2018 2 commits
  4. 18 Jan, 2018 8 commits
  5. 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
  6. 05 Jan, 2018 1 commit
  7. 04 Jan, 2018 4 commits
  8. 18 Dec, 2017 1 commit
  9. 13 Dec, 2017 2 commits
  10. 12 Dec, 2017 1 commit
  11. 10 Dec, 2017 1 commit
    • Ondrej Kozina's avatar
      Derive VK kernel key description from digest id · c7403246
      Ondrej Kozina authored
      Originally the key description for VK was derived
      from segment id. This could lead to ambiguity when
      keyslot key is verified and loaded in kernel keyring
      using activation functions with CRYPT_ACTIVATE_KEYRING_KEY
      flag raised.
      c7403246
  12. 09 Dec, 2017 3 commits
  13. 07 Dec, 2017 4 commits
  14. 06 Dec, 2017 1 commit
  15. 05 Dec, 2017 1 commit
  16. 01 Dec, 2017 2 commits
  17. 30 Nov, 2017 1 commit
  18. 24 Nov, 2017 1 commit