Now recursively create more layers until you have barely any free space left on the disk, then do some performance benchmarks. ;)
Linux
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
Yeah, LUKS and most block level overlays just don't care. That's what good abstraction layers do for you!
You can LUKS on a disk image mounted over SSHFS that itself resides on a Ceph cluster and mounted over iSCSI for all it cares. Is it a block device? Yes? Good to go.
You can even LUKS a floppy if you want. Or a CD.
I remember years ago investigating alternatives to VMware vSAN and doing hyperconverged storage clusters in Red Hat with glusterFS in top of a couple of other layers. Feels rickety as heck putting it all together but it works well. Hard sell for “normal” people who expect to hit a Next button and get some pretty graphical chart though.
we really ain't making any jokes on the name of the drives? okay...
Yes, perhaps I should have named them outerLuks
and innerLuks
... oh well lol
Actually the bottomLuks generates most of the power.
Speed has everything to do with it.
Well considdering it was posted by a user with the username "communism" i will assume bottomLuks
That's cool and I hope I never see that in the wild
Why not?
Seems like it would be fairly inefficient having to encrypt and decrypt data twice.
You can, sure, but you probably shouldn't. Encrypting and decrypting consume additional cpu time, and you won't gain much in terms of security.
not really if you have a hardware chip that does the encrypt/decrypting
AES has been accelerated on all Intel CPUs since Broadwell, was common as far back as Sandy Bridge, and has been available since Westmere.
AMD has had AES acceleration since Bulldozer.
But the commenter is right that adding a second layer of encryption is useless in everything except very specific circumstances.
Yes, but as I've found recently AES-NI is only as good as your software support for it. Had a team using an ancient version of winscp and they kept complaining about download speeds on our 10Gb circuit. Couldn't replicate it on any other machine with the newest version of winscp so I installed their exact version. AES-NI support wasn't added until like 2020 and it gave them 5x better download speed after upgrading.
I've also found about this recently when moving my root from drive to drive which was after I upgraded to 13th gen intel (from various older i5s) and the best cipher changed (cryptsetup benchmark
).
agreed that it is useless for most cases but I could see it being useful if you need multiple people to agree on decrypting a file.
multiple people to agree on decrypting a file
For that, you would use Shamir's Secret Sharing algorithm rather than multiple encryption.
That's pretty nitty although you can always just partition a long key and distribute the partitions to the different people
there's always more than one way to skin a rat
Does cryptsetup/luks do that? I thought that was only software encryption.
it depends if your hardware supports the algos that cryptsetup/luks use I guess....
Of course, and you can also add on as many layers of LVM and MDADM as you'd like.
You can also do the same with disk images (including sparse images)
Above and/or below LUKS!
So these days I use LVMRAID instead of mdraid. Underneath it uses mdraid but it's a bit easier to use since it's self-contained in LVM.