Possible to setup open LUKS without entering a password at boot time?

Labbing on open LUKS tonight, and things are going well.
Was wondering if its possible not to have to enter a password for the partition that is encrypted, while the RHEL OS is booting up? I mean is there any other place to enter it so that the OS boots up without having to enter the password? Hopefully what I'm asking makes sense.
I did notice that under /boot/grub.conf there is an entry
Jang in Chp 5 refers to this entry as
So that means if I were to remove that, it won't detect the volume that is encrypted?
Was wondering if its possible not to have to enter a password for the partition that is encrypted, while the RHEL OS is booting up? I mean is there any other place to enter it so that the OS boots up without having to enter the password? Hopefully what I'm asking makes sense.
I did notice that under /boot/grub.conf there is an entry
rd_NO_LUKS
Jang in Chp 5 refers to this entry as
disables detection of volumes encrypted to the LUKS system.
So that means if I were to remove that, it won't detect the volume that is encrypted?
***Freedom of Speech, Just Watch What You Say*** Example, Beware of CompTIA Certs (Deleted From Google Cached)
"Its easier to deceive the masses then to convince the masses that they have been deceived."
-unknown
"Its easier to deceive the masses then to convince the masses that they have been deceived."
-unknown
Comments
Follow these steps and you can mount on boot filesystem:
Part 1: preparing and testing
Part 2: add key and mount on boot
And that's it
rd_NO_LUKS is a kernel parameter - the kernel will not look for LUKS encrypted volumes. therefore will be no attempts to find key files,passphrase prompts and so on.
I disagree - If you know what you're doing there is no place for an error.
And you can always add rd_NO_LUKS to kernel parameters or boot from CD/DVD/USB and fix the crypttab file. Of course you have to protect/backup/copy to safe place your key file
You are of course entitled to your opinion. I stand by my comment. The crypttab is an area which can and does cause issues - extra care should be taken.
You can still recover by booting into Single mode and fixing it. Happened to me while labbing. I had to think back in my head the steps I took and I realized I missed /etc/crypttab.
"Its easier to deceive the masses then to convince the masses that they have been deceived."
-unknown
Case in point ...