AnnouncementsMatrixEventsFunnyVideosMusicBooksProjectsAncapsTechEconomicsPrivacyGIFSCringeAnarchyFilmPicsThemesIdeas4MatrixAskMatrixHelpTop Subs
4
Add topics

Comment preview

[-]x0x70(0|0)

Unless you have Linux and LUKS it yourself, it isn't encrypted.

You don't even need to partition to play with it.

fallocate -l 16G encrypted_dir.img
cryptsetup luksFormat encrypted_dir.img
sudo cryptsetup open encrypted_dir.img encrypted_dir  
sudo mkfs.ext4 /dev/mapper/encrypted_dir

# We just finished the hard part that only has to be done once
# The rest is super straight forward.

# Mount it
mkdir encrypted_dir
sudo mount /dev/mapper/ecrypted_dir encrypted_dir
#Close it
sudo umount encrypted_dir
sudo cryptsetup close /dev/mapper/encrypted_dir
#Re-open
sudo cryptsetup open encrypted_dir.img encrypted_dir
sudo mount /dev/mapper/encrypted_dir encrypted_dir

Setting up full system encryption is better. But if you didn't do that it doesn't mean you can't use LUKS. FYI, disk images as files are very convenient. If you ever run out of available partitions and don't want to learn LVM, just mkfs.ext4 a file to save a partition as a file. Yes you can do that.

[-]LarrySwinger
0(0|0)

It requires you to allocate a certain amount of space to it, which is much less convenient than Sparsebundles on macOS. Those require space allocation as well, but the bundle consists of small files (like 4kb) that get assembled into the virtual disk upon decryption. As a result, it doesn't take any more space than the files in encrypted form do and you're really just setting a limit for the size. One of my gripes with GNU is that it doesn't get this right.