Sponsored Content
Operating Systems Linux Debian Problems with cryptsetup keyfile encrypted root partition under Debian 9, i386 Post 303024537 by tyuxar on Wednesday 10th of October 2018 11:51:50 AM
Old 10-10-2018
I am trying to create a Debian 9 system with the root partition encrypted with a keyfile which is stored on a different (and unformatted) partition. And the aim is to get the keyfile at boot automatically, so the machine asking for the password at boot is not the desired effect.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Partition Problems

I just finished installing Solaris 5.8 and I tried to install StarOffice, it said I was out of room. Now I have a 3 gig HD and I THOUGHT that I gave 512 to swap and kept the rest for storage room. How do I check how much room I have, how would I if I figured out I don't have enough room add... (5 Replies)
Discussion started by: veitcha
5 Replies

2. Linux

partition problems!

Hey, haha i'm back! Just when i thought everythign was working fine and dandy i found out that i screwed up my partitions way back when i set teh computer up like 5 months ago...lol. SO! I have decided to format....jus tcause this is my learning computer and install RH9 or whatever the... (15 Replies)
Discussion started by: byblyk
15 Replies

3. Solaris

increasing root / partition

Dear all, I have a root partition which is 20 G in size. I have var and /tmp as seperate file systems. But this 20 G of root is not sufficeint. I want to increase the size of the / partition. Is there any way to increase with out down time. my df -k output is Filesystem ... (4 Replies)
Discussion started by: jegaraman
4 Replies

4. IP Networking

iptables forward public IP, no NAT, Debian i386

Hello all, got kinda problem. Have two machines in LAN, one of them connected to Internet directly, another one must be forwarded through the first one. Masquerading works perfectly, but is not what is needed here. Both machines have public IP addresses, when the second machine is forwarded its... (0 Replies)
Discussion started by: Action
0 Replies

5. Solaris

Need to partition root

Hello guys, I am using Solaris 10 x86 OS. While installing OS i have allocated entire 10 GB space to the root. Now i am not able to create new partition it says me "out of range" or "<cylinder number> not expected". Can someone please help me to allocated a default recommended space i.e 8GB or... (2 Replies)
Discussion started by: bhargav90
2 Replies

6. Red Hat

Removing encrypted lvm partition

Hi guys, let me start by saying I appreciate your assistance always. I was practicing how to encrypt partitions in my server. I encrypted an lvm partition using luks and when I tried to remove the partition using lvremove, I get this message Logical volume vg10/lvol1 is used by another... (2 Replies)
Discussion started by: cjashu
2 Replies

7. Ubuntu

Cannot access or boot encrypted drive (gave up waiting for root device...)

I cannot access or boot from my C drive. I'm running Zorin 9 and the drive is a Samsung SSD. The disk was encrypted on install, and that has not given me any problems before. When I start the system it gets to the memory test page, and does not then load the password prompt, which it used to.... (1 Reply)
Discussion started by: David4321
1 Replies

8. Ubuntu

Regarding OS partition and root user

Dear Concern, I am new in ubuntu. Is root user disable in ubuntu? Also, is os partition default in ubuntu? I don't find any feature to create customize mount point to install OS. Below is my current OS partition. amirislam@blnidapp03:~$ df -h Filesystem Size Used... (1 Reply)
Discussion started by: makauser
1 Replies
CRYPTTAB(5)							     crypttab							       CRYPTTAB(5)

NAME
crypttab - Configuration for encrypted block devices SYNOPSIS
/etc/crypttab DESCRIPTION
The /etc/crypttab file describes encrypted block devices that are set up during system boot. Empty lines and lines starting with the "#" character are ignored. Each of the remaining lines describes one encrypted block device, fields on the line are delimited by white space. The first two fields are mandatory, the remaining two are optional. Setting up encrypted block devices using this file supports three encryption modes: LUKS, TrueCrypt and plain. See cryptsetup(8) for more information about each mode. When no mode is specified in the options field and the block device contains a LUKS signature, it is opened as a LUKS device; otherwise, it is assumed to be in raw dm-crypt (plain mode) format. The first field contains the name of the resulting encrypted block device; the device is set up within /dev/mapper/. The second field contains a path to the underlying block device or file, or a specification of a block device via "UUID=" followed by the UUID. The third field specifies the encryption password. If the field is not present or the password is set to "none" or "-", the password has to be manually entered during system boot. Otherwise, the field is interpreted as a absolute path to a file containing the encryption password. For swap encryption, /dev/urandom or the hardware device /dev/hw_random can be used as the password file; using /dev/random may prevent boot completion if the system does not have enough entropy to generate a truly random encryption key. The fourth field, if present, is a comma-delimited list of options. The following options are recognized: discard Allow discard requests to be passed through the encrypted block device. This improves performance on SSD storage but has security implications. cipher= Specifies the cipher to use. See cryptsetup(8) for possible values and the default value of this option. A cipher with unpredictable IV values, such as "aes-cbc-essiv:sha256", is recommended. hash= Specifies the hash to use for password hashing. See cryptsetup(8) for possible values and the default value of this option. keyfile-offset= Specifies the number of bytes to skip at the start of the key file. See cryptsetup(8) for possible values and the default value of this option. keyfile-size= Specifies the maximum number of bytes to read from the key file. See cryptsetup(8) for possible values and the default value of this option. This option is ignored in plain encryption mode, as the key file size is then given by the key size. luks Force LUKS mode. When this mode is used, the following options are ignored since they are provided by the LUKS header on the device: cipher=, hash=, size=. noauto This device will not be automatically unlocked on boot. nofail The system will not wait for the device to show up and be unlocked at boot, and not fail the boot if it does not show up. plain Force plain encryption mode. read-only, readonly Set up the encrypted block device in read-only mode. size= Specifies the key size in bits. See cryptsetup(8) for possible values and the default value of this option. swap The encrypted block device will be used as a swap device, and will be formatted accordingly after setting up the encrypted block device, with mkswap(8). This option implies plain. WARNING: Using the swap option will destroy the contents of the named partition during every boot, so make sure the underlying block device is specified correctly. tcrypt Use TrueCrypt encryption mode. When this mode is used, the following options are ignored since they are provided by the TrueCrypt header on the device or do not apply: cipher=, hash=, keyfile-offset=, keyfile-size=, size=. When this mode is used, the passphrase is read from the key file given in the third field. Only the first line of this file is read, excluding the new line character. Note that the TrueCrypt format uses both passphrase and key files to derive a password for the volume. Therefore, the passphrase and all key files need to be provided. Use tcrypt-keyfile= to provide the absolute path to all key files. When using an empty passphrase in combination with one or more key files, use "/dev/null" as the password file in the third field. tcrypt-hidden Use the hidden TrueCrypt volume. This implies tcrypt. This will map the hidden volume that is inside of the volume provided in the second field. Please note that there is no protection for the hidden volume if the outer volume is mounted instead. See cryptsetup(8) for more information on this limitation. tcrypt-keyfile= Specifies the absolute path to a key file to use for a TrueCrypt volume. This implies tcrypt and can be used more than once to provide several key files. See the entry for tcrypt on the behavior of the passphrase and key files when using TrueCrypt encryption mode. tcrypt-system Use TrueCrypt in system encryption mode. This implies tcrypt. Please note that when using this mode, the whole device needs to be given in the second field instead of the partition. For example: if "/dev/sda2" is the system encrypted TrueCrypt patition, "/dev/sda" has to be given. timeout= Specifies the timeout for querying for a password. If no unit is specified, seconds is used. Supported units are s, ms, us, min, h, d. A timeout of 0 waits indefinitely (which is the default). tmp The encrypted block device will be prepared for using it as /tmp; it will be formatted using mke2fs(8). This option implies plain. WARNING: Using the tmp option will destroy the contents of the named partition during every boot, so make sure the underlying block device is specified correctly. tries= Specifies the maximum number of times the user is queried for a password. The default is 3. If set to 0, the user is queried for a password indefinitely. verify If the encryption password is read from console, it has to be entered twice to prevent typos. At early boot and when the system manager configuration is reloaded, this file is translated into native systemd units by systemd- cryptsetup-generator(8). EXAMPLE
Example 1. /etc/crypttab example Set up four encrypted block devices. One using LUKS for normal storage, another one for usage as a swap device and two TrueCrypt volumes. luks UUID=2505567a-9e27-4efe-a4d5-15ad146c258b swap /dev/sda7 /dev/urandom swap truecrypt /dev/sda2 /etc/container_password tcrypt hidden /mnt/tc_hidden /null tcrypt-hidden,tcrypt-keyfile=/etc/keyfile SEE ALSO
systemd(1), systemd-cryptsetup@.service(8), systemd-cryptsetup-generator(8), cryptsetup(8), mkswap(8), mke2fs(8) systemd 208 CRYPTTAB(5)
All times are GMT -4. The time now is 12:50 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy