On Sun, Jan 27, 2019 at 10:44:52PM +0000, Patrick O'Callaghan wrote:
On Sun, 2019-01-27 at 19:56 +0100, Wolfgang Pfeiffer wrote:
> > Given that encrypting the disk means (at a minimum) reading the entire
> > contents and rewriting it,
> No. I don't think data is written and rewritten. See below.
If it's not being read and rewritten, it's not being encrypted.
Yes, something like that is what I suspect: The actual data on disk
would be left untouched when the *disk/partition* is encrypted. I had
a look through documents explaining luks, and again and again the
topic is "disk" encryption, not "data" encryption. So maybe all that
happens is that - to use a picture - a high security prison (some sort
of crypto layer) is built around the data on disk, while leaving the
actual data untouched, and non-encrypted.
In other words: It seems the file system is encrypted, not the data:
see the already mentioned FAQ: "Create the LUKS container" - at the
end of the section: "Done. You can now use the encrypted file system
to store data"
And what also comes to mind is that when I open (unencrypt) a luks
device, only a second or two after providing the password for the
encrypted disk/partition the partition is unencrypted. I doubt that
this could happen if e.g. a 1 TB partition had all data stored
encrypted on it ..
Or - another possibility - the data stay encrypted after opening the
luks device and will be decrypted only on the fly, just as needed.
No idea, not yet ...
It's as simple as that. A cryptosystem that doesn't read the
You mean, without actually encrypting the data, and instead of that
just some sort of crypto layer around it?
How does that work?
I'd like to know, yes ... :)