<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
	<title type="html"><![CDATA[HyperForum — Cannot encrypt Hyperbola installation]]></title>
	<link rel="self" href="https://forums.hyperbola.info/extern.php?action=feed&amp;tid=232&amp;type=atom" />
	<updated>2019-09-03T22:19:34Z</updated>
	<generator>PunBB</generator>
	<id>https://forums.hyperbola.info/viewtopic.php?id=232</id>
		<entry>
			<title type="html"><![CDATA[Re: Cannot encrypt Hyperbola installation]]></title>
			<link rel="alternate" href="https://forums.hyperbola.info/viewtopic.php?pid=1069#p1069" />
			<content type="html"><![CDATA[<div class="quotebox"><cite>burhen42 wrote:</cite><blockquote><p>I sometimes practise installing Hyperbola on a virtual machine to make sure I know how to do it right for the real thing. Every time I try to encrypt my installation.</p></blockquote></div><p>From <a href="https://forums.hyperbola.info/viewtopic.php?id=233">your other post</a> I conclude, that You&#039;re buying a libreboot device. Libreboot runs GRUB from ROM, so, as You may already know, You can (and should <img src="https://forums.hyperbola.info/img/smilies/smile.png" width="15" height="15" alt="smile" />) do FDE (full disk encryption). Thus, You can encrypt the entire filesystem. The problem is, an emulator will, by default, bahave like a usual BIOS PC. This means, it won&#039;t run it&#039;s own embedded GRUB like Libreboot would, but rather try to run code in the Master Boot Record of the virtual disks provided to it, rendering FDE impossible.<br />The &quot;right&quot; thing to do would be to use <a href="https://libreboot.org/docs/install/#qemu">libreboot rom for qemu</a>. I put double-quotes around &#039;right&#039;, because you could just install GRUB on one virtual disk and fully encrypt the another one...<br />Sorry if I&#039;m telling You sth You&#039;ve already done/learnt by yourself <img src="https://forums.hyperbola.info/img/smilies/tongue.png" width="15" height="15" alt="tongue" /></p><div class="quotebox"><cite>burhen42 wrote:</cite><blockquote><p>Following the instructions, I believe I&#039;m supposed to do it near the beginning by <br />creating a LUKS partition, which I need to start by entering the command &quot;modprobe dm-mod&quot; but the system doesn&#039;t recognise the command.</p><p>What am I missing?</p></blockquote></div><p>What exactly gets outputted? Is <a href="https://www.hyperbola.info/packages/core/x86_64/cryptsetup/">cryptsetup</a> installed?</p><div class="quotebox"><cite>burhen42 wrote:</cite><blockquote><p>Also, if I decide to install in a computer with two hard drives: with my root partition in one drive<br />and my home partition in the second, how do I still encrypt my installation?</p></blockquote></div><p>You&#039;ll have to create 2 LUKS volumes, one on each drive. And You&#039;ll have to tell the system to unencrypt and mount both at boot. Kernel takes care of / using command line parameters passed to it (cryptdevice=device:dmname, etc...). For dealing with /home, use /etc/fstab and /etc/crypttab (didn&#039;t even know such file exists before researching your question <img src="https://forums.hyperbola.info/img/smilies/smile.png" width="15" height="15" alt="smile" />)</p><p>Another option is to have LVM set up on both volumes and LUKS on top of that... But I recommend the first approach</p><div class="quotebox"><cite>burhen42 wrote:</cite><blockquote><p>Plus is it possible to perform a cascaded encryption with LUKS like it is with VeraCrypt?</p></blockquote></div><p>I haven&#039;t heard of such possibility. Is this really desired? I.e. AES has been around for some time and nobody has broken it yet, so it probably won&#039;t happen. Same applies to other ciphers commonly used in LUKS. Hence no need to use one on top of another... unless one wants to advertise with multiple encryption <img src="https://forums.hyperbola.info/img/smilies/big_smile.png" width="15" height="15" alt="big_smile" /></p><p>EDIT: I wrote, that I recommend LVM-on-LUKS over LUKS-on-LVM. After fully reading your other post and some SSD stuff on the net, I think both approaches have their pros and cons. Read on <a href="https://wiki.archlinux.org/index.php/Solid_state_drive#LVM">here</a> and <a href="https://wiki.archlinux.org/index.php/Dm-crypt/Specialties#Discard.2FTRIM_support_for_solid_state_drives_.28SSD.29">here</a>.</p>]]></content>
			<author>
				<name><![CDATA[koszko]]></name>
			</author>
			<updated>2019-09-03T22:19:34Z</updated>
			<id>https://forums.hyperbola.info/viewtopic.php?pid=1069#p1069</id>
		</entry>
		<entry>
			<title type="html"><![CDATA[Cannot encrypt Hyperbola installation]]></title>
			<link rel="alternate" href="https://forums.hyperbola.info/viewtopic.php?pid=1066#p1066" />
			<content type="html"><![CDATA[<p>I sometimes practise installing Hyperbola on a virtual machine to make sure I know how to do it right for the real thing. Every time I try to encrypt my installation.</p><p>Following the instructions, I believe I&#039;m supposed to do it near the beginning by <br />creating a LUKS partition, which I need to start by entering the command &quot;modprobe dm-mod&quot; but the system doesn&#039;t recognise the command.</p><p>What am I missing?</p><p>Also, if I decide to install in a computer with two hard drives: with my root partition in one drive<br />and my home partition in the second, how do I still encrypt my installation?</p><p>Plus is it possible to perform a cascaded encryption with LUKS like it is with VeraCrypt?</p>]]></content>
			<author>
				<name><![CDATA[burhen42]]></name>
			</author>
			<updated>2019-09-03T15:45:59Z</updated>
			<id>https://forums.hyperbola.info/viewtopic.php?pid=1066#p1066</id>
		</entry>
</feed>
