Change ownership of handle to eStorageD object

Clients used to create both the CryptHandle and the eStorageD objects
using the same information. Then the client would pass the CryptHandle
into eStorageD methods in order to perform crypto methods. This change
creates the CryptHandle closer to where it is used. This makes the code
simpler and easier to understand.

Tested:
busctl call xyz.openbmc_project.eStoraged.mmcblk0 \
>    /xyz/openbmc_project/inventory/storage/mmcblk0 \
>    xyz.openbmc_project.Inventory.Item.Volume FormatLuks ays 3 1 2 3 \
>    xyz.openbmc_project.Inventory.Item.Volume.FilesystemType.ext4 \
>    --timeout=60

Change-Id: I276e97146f4498191eb19512bc244a1e8d9cd2cb
Signed-off-by: John Edward Broadbent <jebr@google.com>
4 files changed
tree: 74820acae0d9fd50126c00753b9031565ec53033
  1. include/
  2. src/
  3. subprojects/
  4. .clang-format
  5. .clang-tidy
  6. .gitignore
  7. LICENSE
  8. MAINTAINERS
  9. meson.build
  10. meson_options.txt
  11. OWNERS
  12. README.md
README.md

eStoraged

This daemon serves as an abstraction for an encrypted storage device, encapsulating the security functionality and providing a D-Bus interface to manage the encrypted filesystem on the device. Using the D-Bus interface, other software components can interact with eStoraged to do things like create a new encrypted filesystem, wipe its contents, lock/unlock the device, or change the password.