From: Kalin KOZHUHAROV <me.kalin@gmail.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Ephemeral key lifetime & system sleep
Date: Thu, 8 Dec 2016 11:12:34 +0900 [thread overview]
Message-ID: <CAKXLc7cASvQ+pPGSN2B820W+kHME9hPD8qYLDtNy+JfvVq5Euw@mail.gmail.com> (raw)
In-Reply-To: <87d1h3jszm.fsf@alice.fifthhorseman.net>
On Thu, Dec 8, 2016 at 7:04 AM, Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
> I think scrubbing the ephemeral keys prior to suspend is the right thing
> to do. It's simpler to reason about, sounds straightforward to
> implement, the usability cost isn't that great, and it's likely to be
> the right thing in almost all long-term suspend cases.
>
+1
I never use suspend, except when I need to hack some suspect hardware
(forensics), or ATA SECURITY ERASE a "frozen" drive (anti-forensics).
kill_on_suspend is better, given that it will be auto re-established on resume.
Kalin.
prev parent reply other threads:[~2016-12-08 2:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 21:20 Jason A. Donenfeld
2016-12-07 22:04 ` Daniel Kahn Gillmor
2016-12-08 0:54 ` Jason A. Donenfeld
2016-12-08 2:12 ` Kalin KOZHUHAROV [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=CAKXLc7cASvQ+pPGSN2B820W+kHME9hPD8qYLDtNy+JfvVq5Euw@mail.gmail.com \
--to=me.kalin@gmail.com \
--cc=dkg@fifthhorseman.net \
--cc=wireguard@lists.zx2c4.com \
/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).