On 2/20/25 15:29, Marco Möller wrote:
On 2/20/25 20:48, gene heskett wrote:
On 2/20/25 14:10, Marco Möller wrote:
To my understanding, it makes no sense to perform a TRIM on storage
which is a LUKS2 encyrypted LVM. The storage device should anyway
think that each bit is in use after it was filled with random data
when creating the space. Not only that I cannot imagine how the
storage device should Know what is happening in the encrypted space,
wouldn't it be a security issue if the OS would inform the storage
device about unused space and its location and could actually
perform some kind of a TRIM?
Am I wrong?
Yes. Generally speaking, all file systems know exactly whats in use,
they have to, otherwise they would randomly overwrite another file,
The encryption is only for the data in that allocated space. The file
system knows nothing about that data
If I am right, then, and assuming that TRIM is done by a command
called fstrim, is there a simple command by which I could search
through all cron entries if fstrim would somewhere be defined to
become executed?
.
Cheers, Gene Heskett, CET.
So, the other way round, having a LUKS2 partition and then LVM in it,
that would be the one where TRIM wouldn't make sense? But would be
safer in terms of "hiding" data from spying eyes?
I have zero experience with either. I would say that each likely adds
another layer of complexity, with an accompanying increase in processing
time to decode and make it useful. That in itself might figure into how
difficult it is to gain useful access. I should correct the above
previous statement to declare the file system must know the size of the
file in addition to it location on the media, so it knows where to stop
reading.
.
Cheers, Gene Heskett, CET.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
