From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS - SSD trim
Date: Sat, 24 Apr 2010 19:01:36 +0200 [thread overview]
Message-ID: <20100424170136.GA25497@tansi.org> (raw)
In-Reply-To: <20100424164452.GA11910@linux-m68k.org>
On Sat, Apr 24, 2010 at 06:44:52PM +0200, Richard Zidlicky wrote:
[...]
> very offtopic, I would think there is certainly pressure from various
> agencies and companies not to erase anything. Given that printers are
> programmed to print secret identification patterns on every page there
> could be quite a few surprises lurking in copiers.
Only for color printers. It serves to identify a printer that was
used in couterfiting currency. Storing everything in copiers is
infeasible. Thstorage available is just about enough for the largest
possible print-job, usually not more than 1000 or so different pages.
Given that this limit is routinely exceeded in a day, almost all
pages will not be stored.
> > That is way you use encryoption on top. However, it is higly unlikely
> > current HDDs/SSDs store a lot of information of this type. The storage
> > space is just not there.
>
> most will do clever traffic analysis trying to predict access patterns at
> the very least. Most likely not store everything to survive reboots but
> there can be exceptions.
Sorry, but I openend my SSD. There are just no bits in there for this.
My 30GB SSD has 2GB extra storage, most used for spares for broken
cells. The rest cannot store a lot. In addition, the SSD does not have a
clock that would be essential for adding timestamps to a data access
pattern log.
Here is a story from my country some years back. The federal prolice
wanted to have all emails copied and archived. The ISPs responded
with the query where the cubic-meter of DAT tapes per day should
go? After this (and after realizing the cost, which the police would
have had to pay), the proposal was off the table.
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno@wagner.name
GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F
----
Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
next prev parent reply other threads:[~2010-04-24 16:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 22:48 [dm-crypt] LUKS - SSD trim Felix Blanke
2010-04-21 23:00 ` Milan Broz
2010-04-21 23:03 ` Felix Blanke
2010-04-22 2:17 ` Arno Wagner
2010-04-22 8:42 ` mark
2010-04-22 9:37 ` Milan Broz
2010-04-22 20:12 ` Felix Blanke
2010-04-22 22:20 ` Richard Zidlicky
2010-04-22 22:22 ` Richard Zidlicky
2010-04-23 8:49 ` Milan Broz
2010-04-23 10:20 ` Mikko Rauhala
2010-04-23 11:13 ` Richard Zidlicky
2010-04-23 11:46 ` Milan Broz
2010-04-23 20:09 ` Richard Zidlicky
2010-04-23 20:45 ` Milan Broz
2010-04-23 22:59 ` Richard Zidlicky
2010-04-24 15:59 ` Arno Wagner
2010-04-24 16:44 ` Richard Zidlicky
2010-04-24 17:01 ` Arno Wagner [this message]
2010-04-22 6:17 ` Heinz Diehl
2010-05-14 7:35 ` JG
-- strict thread matches above, loose matches on Subject: below --
2010-05-27 13:14 Christoph Anton Mitterer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100424170136.GA25497@tansi.org \
--to=arno@wagner.name \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.