rootfs encryption support
To add further information to the query , I am executing "cryptsetup" from a recipe as below : (Yocto 2.0.2)
fakeroot do_install() {
cryptsetup --type=plain open hello.enc demomap < dm-crypt-key}
Additional debug log :
+ do_install
| + cryptsetup --type=plain open /path_to/tmp/work/cortexa9hf-vfp-neon-elina-linux-gnueabi/DM-CryptSetup/1.0-r0/hello.enc demomap | Cannot initialize device-mapper. Is dm_mod kernel module loaded? | | Cannot initialize device-mapper. Is dm_mod kernel module loaded? | + bb_exit_handler
Ideally , I was under impression that "fakeroot" shall have allowed to me achieve the goal.
Thanks & Regads
Shrawan
From: Kumar, Shrawan
Sent: Tuesday, September 26, 2017 10:56 AM
To: '[email protected]' <[email protected]>
Subject: rootfs encryption support
Hello Team ,
Is it possible to get encrypted rootfs during image build ?
Currently , I am running "cryptsetup" (as sudo) manually after the final image(rootfs.ext4) is produced . The idea is to get this done within yocto environment without sudo problem .
Thanks and Regards
Shrawan
Hi,
Quoted 14 lines · Shrawan
To add further information to the query , I am executing “cryptsetup” from a recipe as below : (/Yocto 2.0.2)/
fakeroot
do_install(){cryptsetup --type=plain open hello.enc demomap < dm-crypt-key
}
Additional debug log :
+
do_install| + cryptsetup --type=plain open /path_to/tmp/work/cortexa9hf-vfp-neon-elina-linux-gnueabi/DM-CryptSetup/1.0-r0/hello.enc demomap
Quoted 8 lines
| *Cannot initialize device-mapper. Is
dm_modkernel module loaded?*|
| Cannot initialize device-mapper. Is
dm_modkernel module loaded?| +
bb_exit_handler
Your Host kernel need to have support for DM-Crypt enabled, you can autoload the corresponding kernel module by adding to your build host modules configuration:
$ sudo sh -c 'echo dm_mod > /etc/modules-load.d/dm_mod.conf'
Quoted 24 lines
Ideally , I was under impression that “fakeroot” shall have allowed to me achieve the goal.
Thanks & Regads
Shrawan
*From:* Kumar, Shrawan
*Sent:* Tuesday, September 26, 2017 10:56 AM *To:* '[email protected]' <[email protected]> *Subject:* rootfs encryption supportHello Team ,
Is it possible to get encrypted rootfs during image build ?
Currently , I am running “*cryptsetup*” (as sudo) *manually* after the final image(rootfs.ext4) is produced . The idea is to get this done within yocto environment without sudo problem .
Thanks and Regards
Shrawan
A message that is not in the archive (sent off-list or not yet received): [email protected]
When I execute the cryptsetup manually (with sudo ) on the host , I could see " demomap" getting populated . This confirms that it works on host when I run manually and that HOST configuration is OK . However this is not happing under yocto fakeroot environment and it says " Cannot initialize device-mapper. Is dm_mod kernel module loaded?*"
@:~$ ls -l /dev/mapper/ total 0 crw------- 1 root root 10, 236 Sep 15 02:26 control lrwxrwxrwx 1 root root 7 Sep 26 11:56 demomap -> ../dm-7 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lv2swap -> ../dm-6 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lvdocker -> ../dm-1 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lvhome -> ../dm-3 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lvroot -> ../dm-2 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lvswap -> ../dm-5 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lvvar -> ../dm-4 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vgdata-lvdata -> ../dm-0
off course , dm_mod which I could confirm with emty output of lsmod | grep dm_mod But then how does it works on host when I run cryptsetup manually ?
I could see " dm_crypt" module is loaded .
-----Original Message-----
From: Ayoub Zaki [mailto:[email protected]]
Sent: Tuesday, September 26, 2017 4:17 PM
To: Kumar, Shrawan <[email protected]>
Subject: [EXTERNAL] Re: [yocto] rootfs encryption support
Quoted 19 lines · Shrawan
To add further information to the query , I am executing "cryptsetup" from a recipe as below : (/Yocto 2.0.2)/
fakeroot
do_install(){cryptsetup --type=plain open hello.enc demomap < dm-crypt-key
}
Additional debug log :
+
do_install| + cryptsetup --type=plain open /path_to/tmp/work/cortexa9hf-vfp-neon-elina-linux-gnueabi/DM-CryptSetu p/1.0-r0/hello.enc
demomap
Quoted 8 lines
| *Cannot initialize device-mapper. Is
dm_modkernel module loaded?*|
| Cannot initialize device-mapper. Is
dm_modkernel module loaded?| +
bb_exit_handler
*||**Your Host kernel need to have support for DM-Crypt enabled, you can autoload the corresponding kernel module by adding to your build host modules configuration:
$ sudo sh -c 'echo dm_mod > /etc/modules-load.d/dm_mod.conf'* || **
Quoted 17 lines
Ideally , I was under impression that "fakeroot" shall have allowed to me achieve the goal.
Thanks & Regads
Shrawan
*From:* Kumar, Shrawan
*Sent:* Tuesday, September 26, 2017 10:56 AM *To:* '[email protected]' <[email protected]> *Subject:* rootfs encryption supportHello Team ,
Is it possible to get encrypted rootfs during image build ?
Quoted 10 lines
Currently , I am running "*cryptsetup*" (as sudo) *manually* after the final image(rootfs.ext4) is produced . The idea is to get this done within yocto environment without sudo problem .
Thanks and Regards
Shrawan
--
Ayoub Zaki
Embedded Systems Consultant
Vaihinger Straße 2/1
D-71634 Ludwigsburg
Tel. : +4971415074546
Mobile : +4917662901545
Email : [email protected]
Homepage : https://clicktime.symantec.com/a/1/8fQ575pM7qUybRZBFjM9C7WPhR2dXT1R4k3d_4A9BOc=?d=Tm5cGpFBEW_vK6_eBrh-lyBQV_R1miTaoqmkTnsHhnTjNs9fOY92cq9wfN5CbL76p9_yEC-LnqRTAKlF1fzjPCBupycsjT3GP6G75yD1UVlxZ7c2mqLgkyrhClC1V-74zP2Zbhs8BAnSEhpjJoqPP_0JU1Lzuo-iK8U_D7B1zQes8b4JBgf3DPo21HUsMa2qEGMbeqEDq7LU4y2SXKadgb1xcCNmOTvQIJ9LchpVyTITF0Qw2c5M1--o9oWn7FlThc-KBs5TLfBKAIexE3ndzKZOdu9D2NlCmcrEM7q1Oe8sarufZ71B8FsfvU5lT_9gB-hfFD0PEgEJY8VxBGtY4-tLfyAnaY8Z-BlIlSDBgZeorcaKkAzCj4nQTbXIWTTIYg%3D%3D&u=https%3A%2F%2Fembexus.com
Quoted 19 lines · Shrawan
When I execute the cryptsetup manually (with sudo ) on the host , I could see " demomap" getting populated . This confirms that it works on host when I run manually and that HOST configuration is OK . However this is not happing under yocto fakeroot environment and it says " Cannot initialize device-mapper. Is
dm_modkernel module loaded?*"@:~$ ls -l /dev/mapper/ total 0 crw------- 1 root root 10, 236 Sep 15 02:26 control lrwxrwxrwx 1 root root 7 Sep 26 11:56 demomap -> ../dm-7 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lv2swap -> ../dm-6 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lvdocker -> ../dm-1 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lvhome -> ../dm-3 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lvroot -> ../dm-2 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lvswap -> ../dm-5 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vg00-lvvar -> ../dm-4 lrwxrwxrwx 1 root root 7 Sep 15 02:26 vgdata-lvdata -> ../dm-0
Quoted 6 lines
off course ,
dm_modwhich I could confirm with emty output of lsmod | grepdm_mod
But then how does it works on host when I run cryptsetup manually ?I could see "
dm_crypt" module is loaded .
I could not get around needing sudo, and ended up enabling passwordless sudo for the user doing the build. Inside the fakerooted function, pieces that don't require sudo look like this:
cryptsetup luksFormat ...
while others that do require sudo look like this:
PSEUDO_UNLOAD=1 sudo cryptsetup open ...
The PSEUDO_UNLOAD might just be cosmetic in that it prevents a warning about not being able to load libpseudo.so; I don't remember if it's actually required. But it does make it clear that the command done by the sudo is not in the fakeroot environment.
The root of the problem is that going through device mapper requires real root, fakeroot doesn't give you that, and luks (as far as I can tell) can only work through device mapper. You might be about to write your own luks header with the keys, encrypt it sector-by-sector yourself, blah blah blah.
I *did* want to see if I could avoid luks altogether: encrypt it raw using an image postprocessing command, then at runtime map it with dm-crypt (vs. luks), but never got around to it. That should be possible without sudo, and not having luks seems like it would be okay for many embedded uses.
Quoted 97 lines
-----Original Message-----
From: Ayoub Zaki [mailto:[email protected]]
Sent: Tuesday, September 26, 2017 4:17 PM
To: Kumar, Shrawan <[email protected]>
Subject: [EXTERNAL] Re: [yocto] rootfs encryption supportQuoted 19 lines · Shrawan
To add further information to the query , I am executing "cryptsetup"
from a recipe as below : (/Yocto 2.0.2)/fakeroot
do_install(){cryptsetup --type=plain open hello.enc demomap <dm-crypt-key
}
Additional debug log :
+
do_install| + cryptsetup --type=plain open /path_to/tmp/work/cortexa9hf-vfp-neon-elina-linux-gnueabi/DM-CryptSetu p/1.0-r0/hello.enc
demomapQuoted 8 lines
| *Cannot initialize device-mapper. Is
dm_modkernel module loaded?*|
| Cannot initialize device-mapper. Is
dm_modkernel module loaded?| +
bb_exit_handler*||**Your Host kernel need to have support for DM-Crypt enabled, you can autoload the corresponding kernel module by adding to your build host modules configuration:
$ sudo sh -c 'echo dm_mod > /etc/modules-load.d/dm_mod.conf'* || **Quoted 17 lines
Ideally , I was under impression that "fakeroot" shall have allowed to me achieve the goal.
Thanks & Regads
Shrawan
*From:* Kumar, Shrawan
*Sent:* Tuesday, September 26, 2017 10:56 AM *To:* '[email protected]' <[email protected]> *Subject:* rootfs encryption supportHello Team ,
Is it possible to get encrypted rootfs during image build ?
Quoted 10 lines
Currently , I am running "*cryptsetup*" (as sudo) *manually* after
the final image(rootfs.ext4) is produced . The idea is to get this done within yocto environment without sudo problem .Thanks and Regards
Shrawan
--
Ayoub Zaki
Embedded Systems ConsultantVaihinger Straße 2/1
D-71634 LudwigsburgTel. : +4971415074546
Mobile : +4917662901545
Email : [email protected]
Homepage : https://clicktime.symantec.com/a/1/
8fQ575pM7qUybRZBFjM9C7WPhR2dXT1R4k3d_4A9BOc=?d=Tm5cGpFBEW_vK6_eBrh-lyBQV_ R1miTaoqmkTnsHhnTjNs9fOY92cq9wfN5CbL76p9_yEC- LnqRTAKlF1fzjPCBupycsjT3GP6G75yD1UVlxZ7c2mqLgkyrhClC1V- 74zP2Zbhs8BAnSEhpjJoqPP_0JU1Lzuo-iK8U_D7B1zQes8b4JBgf3DPo21HUsMa2qEG MbeqEDq7LU4y2SXKadgb1xcCNmOTvQIJ9LchpVyTITF0Qw2c5M1--o9oWn7FlThc-KBs5TLfBKAIexE3ndzKZOdu9D2NlCmcrEM7q1Oe8sarufZ71B8FsfvU5lT_9gB-hfFD0PEgEJY8VxBGtY4-tLfyAnaY8Z-BlIlSDBgZeorcaKkAzCj4nQTbXIWTT IYg%3D%3D&u=https%3A%2F%2Fembexus.com--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto