Useful for setting up dm-verity during a build.
"native-sdk" gets added just in case that this may also be used in an
SDK.
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
cryptsetup luksOpen (luksFormat) uses xts by default.
When the module is not installed, cryptsetup prints:
Check that kernel supports aes-xts-plain64 cipher (check syslog for more info)
Signed-off-by: Bogdan Hopulele <bogdan.hopulele@ni.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* there is PACKAGECONFIG for libgcrypt, but do_configure fails
without macro staged by libgcrypt:
configure.ac:122: error: possibly undefined macro: AM_PATH_LIBGCRYPT
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* This change is only aesthetic (unlike indentation in Python
tasks).
* Some recipes were using tabs.
* Some were using 8 spaces.
* Some were using mix or different number of spaces.
* Make them consistently use 4 spaces everywhere.
* Yocto styleguide advises to use tabs (but the only reason to keep
tabs is the need to update a lot of recipes). Lately this advice
was also merged into the styleguide on the OE wiki.
* Using 4 spaces in both types of tasks is better because it's less
error prone when someone is not sure if e.g.
do_generate_toolchain_file() is Python or shell task and also allows
to highlight every tab used in .bb, .inc, .bbappend, .bbclass as
potentially bad (shouldn't be used for indenting of multiline
variable assignments and cannot be used for Python tasks).
* Don't indent closing quote on multiline variables
we're quite inconsistent wheater it's first character on line
under opening quote or under first non-whitespace character in
previous line.
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Acked-by: Koen Kooi <koen@dominion.thruhere.net>
Cryptsetup with the command luksOpen failed with the error message:
device-mapper: status ioctl failed: Permission denied
The error comes from libgcrypt with drops root privileges if it is
linked with libcap support [1]. Update cryptsetup to latest version,
add PACKAGECONFIG for crypto backend selection (openssl / gcrypt)
and change the default crypto backend to openssl as libgcrypt states
the drop root privileges behaviour as a feature [2].
The license was updated to GPLv2 with OpenSSL exception.
Update the RRECOMMENDS to be conistent with the package names.
[1] http://code.google.com/p/cryptsetup/issues/detail?id=47
[2] https://bugs.g10code.com/gnupg/issue1181
Signed-off-by: Stefan Herbrechtsmeier <stefan@herbrechtsmeier.net>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
* add LIC_FILES_CHKSUM
* depend on util-linux (renamed from util-linux-ng)
* depend on lvm2 instead of device-mapper
* inherit gettext
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
