Displaying 20 results from an estimated 3000 matches similar to: "CentOS 6 and crypttab"
2017 Jun 20
2
CentOS 6 and luksOpen
Leon Fauster wrote:
>> Am 20.06.2017 um 16:53 schrieb m.roth at 5-cent.us:
>>
>> Upgraded a RAID. Copied everything from backup.
>>
>> And then my manager said I had to encrypt the drive.
>>
>> I've done that, and made the filesystem, but I can't mount it.
>>
>> CentOS 6.
>> I have the entry in /etc/crypttab, and a key in
2017 Jun 20
2
CentOS 6 and luksOpen
Upgraded a RAID. Copied everything from backup.
And then my manager said I had to encrypt the drive.
I've done that, and made the filesystem, but I can't mount it.
CentOS 6.
I have the entry in /etc/crypttab, and a key in /etc/crypt.pw, and the
luks UUID in /etc/fstab. I cannot find the command that tells it to create
the device in /dev/mapper from the info in /etc/crypttab.
Clues for
2015 Feb 10
1
LUKS on EL6 / enable block device after reboot
Is there an easy way (cli) to enable a luks encrypted partition
after reboot (a partition that was not enabled while booting,
because not in the crypttab).
I can execute the necessary command stack [1] but just wondering if
there is an "enterprise/easy" way to do that ...
[1] cryptsetup luksOpen $(blkid -t TYPE="crypto_LUKS" -o device) \
luks-$(cryptsetup luksUUID
2009 Jan 22
1
Contribute to Centos wiki
I'd like to edit the HowTo/EncryptedFilesystem page the note on how to
create a valid keyfile. This is not a trivial action.
Creating a plaintext file in vim does not qualify as a valid
password. Instead, a valid keyfile is created by doing the following:
echo -n "password" > keyfile.key
which explicitly creates the file with password on the first line with
an explicit
2015 Mar 06
3
LVM encryption and new volume group
Hi Chris,
thanks for your answer.
It is the first time I decided to encrypt my lvm. I choosed to encrypt the volume group, not every logical volume itself, because in case of doing lvm snapshots in that group they will be encrypted too?
And how do I create a new encrypted volume group?
Regards
Tim
Am 6. M?rz 2015 01:58:23 MEZ, schrieb Chris Murphy <lists at colorremedies.com>:
>On
2019 Jul 23
2
mdadm issue
Just rebuilt a C6 box last week as C7. Four drives, and sda and sdb for
root, with RAID-1 and luks encryption.
Layout:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE
MOUNTPOINT
sda 8:0 0 931.5G 0 disk
??sda1 8:1 0 200M 0 part
/boot/efi
??sda2
2015 Mar 08
1
LVM encryption and new volume group
I'm sorry, but grep -i crypt /var/log/anaconda/anaconda.program.log
returns nothing. But I have got an entry in /etc/crypttab.
I only found this with grep -i luks /var/log/anaconda/anaconda.*:
/var/log/anaconda/anaconda.storage.log:20:47:55,959 DEBUG blivet:
LUKS.__init__:
/var/log/anaconda/anaconda.storage.log:20:49:25,009 DEBUG storage.ui:
LUKS.__init__:
2020 Oct 06
2
Re: [PATCH common v2 4/4] options: Ignore errors from guestfs_luks_uuid.
On Mon, Sep 07, 2020 at 10:41:20AM +0100, Richard W.M. Jones wrote:
>For BitLocker disks cryptsetup does not (yet? ever?) support reading
>UUIDs and this function will fail. This does not matter here so just
>ignore the error.
>
>Note there is no error message, cryptsetup simply returns with a bad
>exit code:
>
>><rescue> cryptsetup luksUUID /dev/sda2
2020 Sep 07
5
[PATCH common v2 0/4] Windows BitLocker support.
For links to the original patch series, see:
https://bugzilla.redhat.com/show_bug.cgi?id=1808977#c8
The original feedback was that ignoring errors from guestfs_luks_uuid
would ignore legitimate errors from non-BitLocker disks, so I have
modified this series so that errors are only ignored in the BitLocker
case. As noted in the 4th patch there is no actual error in the
BitLocker case, cryptsetup
2020 Oct 07
2
Re: [PATCH common v2 4/4] options: Ignore errors from guestfs_luks_uuid.
On Tue, Oct 06, 2020 at 03:06:54PM +0100, Richard W.M. Jones wrote:
>On Tue, Oct 06, 2020 at 03:25:20PM +0200, Martin Kletzander wrote:
>> On Mon, Sep 07, 2020 at 10:41:20AM +0100, Richard W.M. Jones wrote:
>> >For BitLocker disks cryptsetup does not (yet? ever?) support reading
>> >UUIDs and this function will fail. This does not matter here so just
>> >ignore
2017 Jun 20
0
CentOS 6 and luksOpen
> Am 20.06.2017 um 17:12 schrieb m.roth at 5-cent.us:
>
> Leon Fauster wrote:
>>> Am 20.06.2017 um 16:53 schrieb m.roth at 5-cent.us:
>>>
>>> Upgraded a RAID. Copied everything from backup.
>>>
>>> And then my manager said I had to encrypt the drive.
>>>
>>> I've done that, and made the filesystem, but I can't
2015 Mar 06
1
LVM encryption and new volume group
On 03/05/2015 06:58 PM, Chris Murphy wrote:
> On Thu, Mar 5, 2015 at 2:09 PM, Tim <lists at kiuni.de> wrote:
>> Hello list,
>>
>> I bought a Thinkpad T420 and installed CentOS 7 recently.
>>
>> I choosed to use lvm encryption for the entire volume group. It works so far.
>>
>> But now I am planning to install a second hard disk. My thought is to
2017 Jun 20
0
CentOS 6 and luksOpen
> Am 20.06.2017 um 16:53 schrieb m.roth at 5-cent.us:
>
> Upgraded a RAID. Copied everything from backup.
>
> And then my manager said I had to encrypt the drive.
>
> I've done that, and made the filesystem, but I can't mount it.
>
> CentOS 6.
> I have the entry in /etc/crypttab, and a key in /etc/crypt.pw, and the
> luks UUID in /etc/fstab. I cannot
2017 Feb 03
0
tmp option of crypttab
I have successfully used the swap option of crypttab (# man crypttab)
to encrypt the swap partition dynamically. rc.sysinit enables that
swap partition successfully at the right point (after encryption).
The same doesn't work for the tmp option of crypttab (# man crypttab).
The encrypted partition is present after booting the system. Manually
mounting it works but adding
2018 Nov 27
1
NBDE, clevis and tang for non-root disk
Radu Radutiu wrote:
> On Tue, Nov 27, 2018 at 3:14 PM mark <m.roth at 5-cent.us> wrote:
>
>> What we do is to have the encryption key of the secondary filesystem in
>> /etc/crypttab, which is, of course, 600. As it boots, it decrypts from
>> that as it mounts the rest of the system.
>>
> Thanks, this is working as expected and it gave me the hint needed to
2008 Oct 15
2
Encrypting tmp swap and home
Hi everyone,
I added a page under the HowTos for Encryption, and then added a guide
for encrypting /tmp /swap and /home using cryptsetup and LUKS keys on
LVM, when you already have partitions setup.
http://wiki.centos.org/HowTos/EncryptTmpSwapHome
Regards,
Max
2019 Jul 23
1
mdadm issue
> Am 23.07.2019 um 22:39 schrieb Gordon Messmer <gordon.messmer at gmail.com>:
>
> I still don't understand how this relates to md125. I don't see it referenced in mdadm.conf. It sounds like you see it in the output from lsblk, but only because you manually assembled it. Do you expect there to be a luks volume there?
To check:
cryptsetup isLuks <device>
2019 Jul 23
2
mdadm issue
Gordon Messmer wrote:
> On 7/23/19 11:12 AM, mark wrote:
>
>> Now, cryptsetup gives me the same UUID as I have in /etc/mdadm.conf.
>> The
>> entry in /etc/crypttab looks identical to the RAIDs for root and swap,
>> but nope.
>
>
> Can you post those files somewhere?? I'm confused by the idea that
> cryptsetup is involved in or using the same UUID as an
2008 Aug 28
3
potential wiki on encryption
Hello all,
I posted the whole disk encryption instructions in the forum that has been briefly discussed on the list. I joined the list per Ned's post on the thread.
http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&topic_id=15923&forum=42
I have a couple of questions about the process of creating a wiki.
1. How does the peer-review process work?
2. Is there a place
2010 Jul 21
0
[PATCH] RFC: Encrypted swap support
(depends on Advance Storage Configuration patch)
This patch adds the option of requesting, at install time, that swap LVs be encrypted. The modifications include:
* Introduction of the ovirt_swap_encrypt install parameter
* Inclusion of all required packages
* Inclusion of required kernel modules
* Introduction of /etc/ovirt-crypttab to hold encrypted swap configuration (Couldn't use