From: Eric Biggers <ebiggers@kernel.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Pascal Van Leeuwen <pvanleeuwen@insidesecure.com>,
Christophe Leroy <christophe.leroy@c-s.fr>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: another testmgr question
Date: Fri, 24 May 2019 18:22:59 -0700 [thread overview]
Message-ID: <20190525012258.GC713@sol.localdomain> (raw)
In-Reply-To: <CAKv+Gu_Pxv97rpt7Ju0EdtFnXqp3zoYfHtm1Q51oJSGEAZmyDA@mail.gmail.com>
On Fri, May 24, 2019 at 11:25:52AM +0200, Ard Biesheuvel wrote:
>
> All userland clients of the in-kernel crypto use it specifically to
> access h/w accelerators, given that software crypto doesn't require
> the higher privilege level (no point in issuing those AES CPU
> instructions from the kernel if you can issue them in your program
> directly)
Unfortunately people also use AF_ALG because they're too lazy to use a userspace
crypto library, e.g. systemd uses it for HMAC-SHA256, and iproute2 uses it for
SHA-1.
- Eric
next prev parent reply other threads:[~2019-05-25 1:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM6PR09MB3523CED0B1587FCBDE4095A0D2010@AM6PR09MB3523.eurprd09.prod.outlook.com>
[not found] ` <20190523185833.GA243994@google.com>
2019-05-23 19:32 ` another testmgr question Pascal Van Leeuwen
2019-05-23 20:05 ` Eric Biggers
2019-05-23 21:43 ` Pascal Van Leeuwen
2019-05-23 23:48 ` Eric Biggers
2019-05-24 8:44 ` Pascal Van Leeuwen
2019-05-24 8:46 ` Christophe Leroy
2019-05-24 8:49 ` Jeffrey Walton
2019-05-24 9:42 ` Pascal Van Leeuwen
2019-05-24 9:21 ` Pascal Van Leeuwen
2019-05-24 9:25 ` Ard Biesheuvel
2019-05-24 9:34 ` Pascal Van Leeuwen
2019-05-24 9:45 ` Ard Biesheuvel
2019-05-24 9:57 ` Pascal Van Leeuwen
2019-05-24 11:09 ` Ard Biesheuvel
2019-05-27 9:52 ` Pascal Van Leeuwen
2019-05-24 10:13 ` Pascal Van Leeuwen
2019-05-24 10:43 ` Kamil Konieczny
2019-05-24 10:54 ` Christophe Leroy
2019-05-27 9:44 ` Pascal Van Leeuwen
2019-05-27 9:49 ` Ard Biesheuvel
2019-05-27 10:04 ` Pascal Van Leeuwen
2019-05-27 10:28 ` Ard Biesheuvel
2019-05-27 10:43 ` Pascal Van Leeuwen
2019-05-27 10:57 ` Ard Biesheuvel
2019-05-27 12:22 ` Pascal Van Leeuwen
2019-05-27 14:59 ` Ard Biesheuvel
2019-05-27 15:56 ` Pascal Van Leeuwen
2019-05-27 16:21 ` Ard Biesheuvel
2019-05-27 20:15 ` Pascal Van Leeuwen
2019-05-27 12:41 ` Pascal Van Leeuwen
2019-05-27 14:45 ` Ard Biesheuvel
2019-05-27 15:16 ` Pascal Van Leeuwen
2019-05-27 15:24 ` Ard Biesheuvel
2019-05-27 20:46 ` Pascal Van Leeuwen
2019-05-25 1:22 ` Eric Biggers [this message]
2019-05-27 9:55 ` Pascal Van Leeuwen
2019-05-24 9:27 ` Stephan Mueller
2019-05-24 5:24 ` Ard Biesheuvel
2019-05-24 7:04 ` Kamil Konieczny
2019-05-24 7:47 ` Pascal Van Leeuwen
2019-05-24 9:15 ` Ard Biesheuvel
2019-05-24 9:28 ` Pascal Van Leeuwen
2019-05-24 6:21 ` Christophe Leroy
2019-05-24 8:04 ` Pascal Van Leeuwen
2019-05-24 6:14 ` Jeffrey Walton
2019-05-24 8:00 ` Pascal Van Leeuwen
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=20190525012258.GC713@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=christophe.leroy@c-s.fr \
--cc=linux-crypto@vger.kernel.org \
--cc=pvanleeuwen@insidesecure.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.