From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: tlhackque <tlhackque@yahoo.com>
Cc: WireGuard Mailing list <wireguard@lists.zx2c4.com>
Subject: Re: CONFIG_ANDROID
Date: Thu, 30 Jun 2022 13:41:43 +0200 [thread overview]
Message-ID: <Yr2L9759Ek63KV1F@zx2c4.com> (raw)
In-Reply-To: <23929467-11c2-cdf2-3841-2a837ba58b51@yahoo.com>
On Thu, Jun 30, 2022 at 06:47:38AM -0400, tlhackque wrote:
> FWIW: Having watched the discussion about CONFIG_ANDROID, it occurs to
> me that there's an alternative for WireGuard that sidesteps the issue.
>
> From the last patcheset, it seems that the only use in WireGuard is to
> avoid clearing keys on every wake-up.
No, it clears keys before sleeping.
>
> So: Why not timestamp key-clear events, and establish a minimum interval?
Because we don't know when we're going to wake up again, and the
objective is to maintain forward secrecy.
Jason
next prev parent reply other threads:[~2022-06-30 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <23929467-11c2-cdf2-3841-2a837ba58b51.ref@yahoo.com>
2022-06-30 10:47 ` CONFIG_ANDROID tlhackque
2022-06-30 11:41 ` Jason A. Donenfeld [this message]
2022-06-30 15:50 ` CONFIG_ANDROID tlhackque
2022-06-30 15:56 ` CONFIG_ANDROID Jason A. Donenfeld
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=Yr2L9759Ek63KV1F@zx2c4.com \
--to=jason@zx2c4.com \
--cc=tlhackque@yahoo.com \
--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).