From: tlhackque <firstname.lastname@example.org>
To: WireGuard Mailing list <email@example.com>
Date: Thu, 30 Jun 2022 06:47:38 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 961 bytes --]
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.
So: Why not timestamp key-clear events, and establish a minimum interval?
It seems to me that this would make WireGuard tolerant of the peculiar
behavior of the Android (handheld) platforms, and expresses what
WireGuard needs - a minimum time between key clearing events. It's also
completely under WireGuard's control, is platform agnostic, and avoids
an inevitable discussion about whether 2 seconds between wakeups is
immutable and satisfies everyone. (If you wait long enough, every
constant eventually becomes a variable...)
Then WireGuard can watch the duststorm over CONFIG_ANDROID's fate settle
out at leisure.
I have no dog in this fight - just an observer.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next parent reply other threads:[~2022-06-30 10:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2022-06-30 10:47 ` tlhackque [this message]
2022-06-30 11:41 ` CONFIG_ANDROID Jason A. Donenfeld
2022-06-30 15:50 ` CONFIG_ANDROID tlhackque
2022-06-30 15:56 ` CONFIG_ANDROID Jason A. Donenfeld
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).