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



Labels:

Comments

Post a Comment

Popular posts from this blog

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...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

"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.
Post a Comment
Read more