From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: [Ksummit-discuss] Fwd: [TECH TALK] Zinc: Minimal Light-weight Kernel Cryptography API
Date: Mon, 24 Sep 2018 03:57:34 +0200 [thread overview]
Message-ID: <CAHmME9ovay9H9PNoAEHpQRFYOOPcsZAHCYYEPL-11mVONBTK4g@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rRnPydFT0CVugiEkVhjHsGukruYqcfdiHu1sSU40A9bQ@mail.gmail.com>
Following up from the other thread, it appears that the below message
was rejected silently by linuxfoundation.org's mailing list server. It
should have been accepted as either:
- 250 2.0.0 Ok: queued as AC122174
- 250 2.0.0 Ok: queued as 8EF1AF8
Hopefully the below submission does make it this time.
(Thanks to James for pointing out that these never made it the first
time around.)
---------- Forwarded message ---------
From: Jason A. Donenfeld <Jason@zx2c4.com>
Date: Fri, Sep 21, 2018 at 6:43 AM
Subject: [TECH TALK] Zinc: Minimal Light-weight Kernel Cryptography API
To: <ksummit-discuss@lists.linuxfoundation.org>
Zinc is a new minimal cryptography API for the kernel that is in the
process of being upstreamed. Rather than providing an abstracted
framework, Zinc provides simple functions. This talk will address the
design considerations of the new API, its approach to implementation
choice and fuzzing, and touch on formally verified cryptography
implementations. We'll explore the difference between, on one hand,
reference code for a particular algorithm, and on the other hand, the
present crypto API with its large and complicated abstractions, and
how Zinc fits into the middle of these extremes. We'll also examine
issues relating to using SIMD from kernel space and the costs
associated with it, and what we can do about it.
prev parent reply other threads:[~2018-09-24 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHmME9oVReKvhpm1CSnF3KLDYtt63SvauHXZ-m6mWR=zno2OJA@mail.gmail.com>
2018-09-24 0:12 ` [Ksummit-discuss] [TECH TALK] WireGuard: Next-Generation Secure Kernel Network Tunnel Jason A. Donenfeld
2018-09-24 0:21 ` James Bottomley
2018-09-24 1:55 ` Jason A. Donenfeld
[not found] ` <CAHmME9rRnPydFT0CVugiEkVhjHsGukruYqcfdiHu1sSU40A9bQ@mail.gmail.com>
2018-09-24 1:57 ` Jason A. Donenfeld [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=CAHmME9ovay9H9PNoAEHpQRFYOOPcsZAHCYYEPL-11mVONBTK4g@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=konstantin@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.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 read-only IMAP folder(s) and NNTP newsgroup(s).