From: Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
To: <noloader@gmail.com>, <linux-crypto@vger.kernel.org>
Subject: Re: How to detect availability of asynchronous ciphers at runtime?
Date: Sat, 26 Mar 2016 20:09:25 +0200 [thread overview]
Message-ID: <56F6D055.1040405@mentor.com> (raw)
In-Reply-To: <CAH8yC8msw5y_fsBM1aGoKXqGAgKfw11YheSt4HJhWogUuZkubg@mail.gmail.com>
On 26.03.2016 20:06, Jeffrey Walton wrote:
> Hi Everyone,
>
> Please forgive my ignorance here... I'm trying to detect the
> availability of asynchronous ciphers support at runtime. The back
> story is there's some feature tests going on based on hard coded
> kernel version numbers (namely, 4.1). I feel like there's probably a
> better way to go about it.
>
> It seems like 'socket(AF_ALG, ...)' is not enough since that only
> detects availability of userland crypto support.
>
> How do I detect the availability of asynchronous ciphers at runtime?
>
> Thank you in advance.
Try this method:
# cat /proc/crypto | egrep '^(name|driver|async|$)'
--
With best wishes,
Vladimir
prev parent reply other threads:[~2016-03-26 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-26 18:06 How to detect availability of asynchronous ciphers at runtime? Jeffrey Walton
2016-03-26 18:09 ` Vladimir Zapolskiy [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=56F6D055.1040405@mentor.com \
--to=vladimir_zapolskiy@mentor.com \
--cc=linux-crypto@vger.kernel.org \
--cc=noloader@gmail.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.