Skip to main content

Encrypt partition using LUKS

At work, I have a desktop running Fedora which has an SSD.  I still am a bit old school, I suppose, and don't have as much confidence in their longevity.  I also realize that this is probably not a valid concern, particularly based on the way I use the disk, which is mostly reads.  Furthermore, I realize that my concern for losing a drive should be addressed in the same manner whether I have an SSD or an archaic spinning platter...

So - I have an external disk which I backup to weekly.  I am moderately concerned about my desktop being compromised by someone at the keyboard, but I am more concerned that someone has the ability to walk by and see my external disk hanging off my PC and try to access it from another PC.  I have a slight advantage of being protected in that the average low-life probably doesn't know anything about Linux.

NOTE: If you are particularly worried about security, do NOT create the keyfile which will force you to enter a passphrase each time.


parted -a none /dev/sdb mklabel gpt
parted -a none /dev/sdb mkpart -- primary ext4 1 -1
parted /dev/sdb unit b print

dd if=/dev/urandom of=/root/.kyfl bs=1024 count=4
chmod 0400 /root/.kyfl

yum install cryptsetup-luks
cryptsetup -y -v luksFormat /dev/sdb1

WARNING!
========
This will overwrite data on /dev/sdb1 irrevocably.

Are you sure? (Type uppercase yes): YES
Enter LUKS passphrase:
Verify passphrase:
echo <PassPhrase> | cryptsetup luksAddKey /dev/sdb1 /root/.kyfl

cryptsetup luksOpen --key-file /root/.kyfl /dev/sdb1 backups
mkdir /backups
mkfs.ext4 /dev/mapper/backups
mount /dev/mapper/backups /backups/
umount /backups
cryptsetup luksClose backups

echo "backups /dev/sdb1 /root/.kyfl luks" >> /etc/crypttab
echo "/dev/mapper/backups /backups ext4 defaults 0 2" >>
/etc/fstab



Comments

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...