From: Aleksa Sarai <cyphar@cyphar.com>
To: wireguard@lists.zx2c4.com
Subject: New Verified ChaCha20-Poly1305 Paper
Date: Mon, 6 May 2019 19:32:45 +1000 [thread overview]
Message-ID: <20190506093245.w4mlnvggtuei5pia@yavin> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 783 bytes --]
I just saw this paper[1] which claims to have an implementation of
ChaCha20-Poly1305 in vectorised assembly using a method which
"deliver[s] formally verified vectorized implementations which
outperform the fastest non-verified code"
Is there any interest in using this for Zinc (it's my understanding[2]
that the ChaCha20 and Poly1305 code in Zinc is *not* formally verified)?
The repo is [3]. It looks like they don't have verified generic C
implementations unfortunately, but aren't there verified C versions in
HACL*?
[1]: https://arxiv.org/abs/1904.04606
[2]: https://marc.info/?l=linux-kernel&m=155405777331772&w=2
[3]: https://github.com/tfaoliveira/libjc
--
Aleksa Sarai
Senior Software Engineer (Containers)
SUSE Linux GmbH
<https://www.cyphar.com/>
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
reply other threads:[~2019-05-06 20:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20190506093245.w4mlnvggtuei5pia@yavin \
--to=cyphar@cyphar.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).