From: Glynn Clements <glynn@gclements.plus.com>
To: "Fred ." <eldmannen@gmail.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: Protect against cold boot attacks?
Date: Thu, 24 Nov 2011 20:45:20 +0000 [thread overview]
Message-ID: <20174.44256.195550.595437@cerise.gclements.plus.com> (raw)
In-Reply-To: <CAJgfmqXArW9JmgaJ+Z=tDVgu8ZscKLFS_6AWUjh15eg2rVa48Q@mail.gmail.com>
Fred . wrote:
> Will
> su-c 'sync; echo 3 > /proc/sys/vm/drop_caches'
> protect against cold boot attacks?
No. Writing to drop_caches releases the memory for subsequent re-use;
it doesn't overwrite it, so anything stored in that memory is still
susceptible to a cold-boot attack.
> Is there anything that will protect against cold boot attacks?
Physical security.
Other than that, it's a matter of degree. Particularly sensitive
information (passwords, encryption keys) should be overwritten by the
application once they are no longer required. Larger amounts of
application data (i.e. documents) can't really avoid being held in
RAM.
--
Glynn Clements <glynn@gclements.plus.com>
prev parent reply other threads:[~2011-11-24 20:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 23:20 Protect against cold boot attacks? Fred .
2011-11-24 20:45 ` Glynn Clements [this message]
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=20174.44256.195550.595437@cerise.gclements.plus.com \
--to=glynn@gclements.plus.com \
--cc=eldmannen@gmail.com \
--cc=linux-admin@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).